…262)

Forwards `tags` and `target_compatible_with` to the generated targets
from `cc_fuzz_test`, `java_fuzz_test` and `fuzzing_decoration`.

Being able to modify tags and specify platform constraints is frequently
needed in CI/CD integrations.

Welcome to [Renovate](https://redirect.github.com/renovatebot/renovate)!
This is an onboarding PR to help you understand and configure settings
before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate,
simply close this Pull Request unmerged.



---
### Detected Package Files

 * `WORKSPACE` (bazel)
 * `fuzzing/repositories.bzl` (bazel)
 * `MODULE.bazel` (bazel-module)
 * `.bazelversion` (bazelisk)
 * `.github/workflows/bazel_lint.yml` (github-actions)
 * `.github/workflows/bazel_test.yml` (github-actions)
 * `.github/workflows/cpp_lint.yml` (github-actions)
 * `.github/workflows/oss_fuzz.yml` (github-actions)

### Configuration Summary

Based on the default config's presets, Renovate will:

  - Start dependency updates only once this onboarding PR is merged
  - Hopefully safe environment variables to allow users to configure.
  - Show all Merge Confidence badges for pull requests.
  - Enable Renovate Dependency Dashboard creation.
- Use semantic commit type `fix` for dependencies and `chore` for all
others if semantic commits are in use.
- Ignore `node_modules`, `bower_components`, `vendor` and various
test/tests (except for nuget) directories.
  - Group known monorepo packages together.
  - Use curated list of recommended non-monorepo package groupings.
- Show only the Age and Confidence Merge Confidence badges for pull
requests.
  - Apply crowd-sourced package replacement rules.
  - Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add
your custom config to `renovate.json` in this branch. Renovate will
update the Pull Request description the next time it runs.

---

### What to Expect

With your current configuration, Renovate will create 20 Pull Requests:

<details>
<summary>chore(deps): update io_bazel_stardoc digest to
ee7f828</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/io_bazel_stardoc-digest`
  - Merge into: `master`
- Upgrade io_bazel_stardoc to `ee7f82841a96fc9a88cee42ff9d18719d51a792f`


</details>

<details>
<summary>chore(deps): update dependency platforms to v0.0.11</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/platforms-0.x`
  - Merge into: `master`
- Upgrade [platforms](https://redirect.github.com/bazelbuild/platforms)
to `0.0.11`


</details>

<details>
<summary>chore(deps): update dependency abseil-cpp to
v20240116.3</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/abseil-cpp-20240116.x`
  - Merge into: `master`
- Upgrade [abseil-cpp](https://redirect.github.com/abseil/abseil-cpp) to
`20240116.3`


</details>

<details>
<summary>chore(deps): update dependency bazel to v8.3.1</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/bazel-8.x`
  - Merge into: `master`
- Upgrade [bazel](https://redirect.github.com/bazelbuild/bazel) to
`8.3.1`


</details>

<details>
<summary>chore(deps): update dependency bazel_features to
v1.32.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/bazel_features-1.x`
  - Merge into: `master`
- Upgrade
[bazel_features](https://redirect.github.com/bazel-contrib/bazel_features)
to `1.32.0`


</details>

<details>
<summary>chore(deps): update dependency bazel_skylib to v1.8.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/bazel_skylib-1.x`
  - Merge into: `master`
- Upgrade
[bazel_skylib](https://redirect.github.com/bazelbuild/bazel-skylib) to
`1.8.0`


</details>

<details>
<summary>chore(deps): update dependency googletest to v1.17.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/googletest-1.x`
  - Merge into: `master`
- Upgrade [googletest](https://google.github.io/googletest/) to `1.17.0`


</details>

<details>
<summary>chore(deps): update dependency honggfuzz to v2.6</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/honggfuzz-2.x`
  - Merge into: `master`
- Upgrade [honggfuzz](https://redirect.github.com/google/honggfuzz) to
`2.6`


</details>

<details>
<summary>chore(deps): update dependency rules_cc to v0.1.2</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/rules_cc-0.x`
  - Merge into: `master`
- Upgrade [rules_cc](https://redirect.github.com/bazelbuild/rules_cc) to
`0.1.2`


</details>

<details>
<summary>chore(deps): update dependency rules_python to
v0.40.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/rules_python-0.x`
  - Merge into: `master`
- Upgrade
[rules_python](https://redirect.github.com/bazel-contrib/rules_python)
to `0.40.0`
- Upgrade
[rules_python](https://redirect.github.com/bazelbuild/rules_python) to
`0.40.0`


</details>

<details>
<summary>chore(deps): update dependency rules_shell to v0.5.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/rules_shell-0.x`
  - Merge into: `master`
- Upgrade
[rules_shell](https://redirect.github.com/bazelbuild/rules_shell) to
`0.5.0`


</details>

<details>
<summary>chore(deps): update dependency stardoc to v0.8.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/stardoc-0.x`
  - Merge into: `master`
- Upgrade [stardoc](https://redirect.github.com/bazelbuild/stardoc) to
`0.8.0`


</details>

<details>
<summary>chore(deps): update actions/checkout action to v4</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-checkout-4.x`
  - Merge into: `master`
- Upgrade
[actions/checkout](https://redirect.github.com/actions/checkout) to `v4`


</details>

<details>
<summary>chore(deps): update actions/setup-go action to v5</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-setup-go-5.x`
  - Merge into: `master`
- Upgrade
[actions/setup-go](https://redirect.github.com/actions/setup-go) to `v5`


</details>

<details>
<summary>chore(deps): update actions/setup-python action to v5</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-setup-python-5.x`
  - Merge into: `master`
- Upgrade
[actions/setup-python](https://redirect.github.com/actions/setup-python)
to `v5`


</details>

<details>
<summary>chore(deps): update dependency abseil-cpp to
v20250512</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/abseil-cpp-20250512.x`
  - Merge into: `master`
- Upgrade [abseil-cpp](https://redirect.github.com/abseil/abseil-cpp) to
`20250512.1`


</details>

<details>
<summary>chore(deps): update dependency platforms to v1</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/platforms-1.x`
  - Merge into: `master`
- Upgrade [platforms](https://redirect.github.com/bazelbuild/platforms)
to `1.0.0`


</details>

<details>
<summary>chore(deps): update dependency rules_java to v8</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/rules_java-8.x`
  - Merge into: `master`
- Upgrade
[rules_java](https://redirect.github.com/bazelbuild/rules_java) to
`8.13.0`


</details>

<details>
<summary>chore(deps): update dependency rules_python to v1</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/rules_python-1.x`
  - Merge into: `master`
- Upgrade
[rules_python](https://redirect.github.com/bazel-contrib/rules_python)
to `1.5.1`
- Upgrade
[rules_python](https://redirect.github.com/bazelbuild/rules_python) to
`1.5.1`


</details>

<details>
<summary>chore(deps): update dependency ubuntu to v24</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/ubuntu-24.x`
  - Merge into: `master`
- Upgrade [ubuntu](https://redirect.github.com/actions/runner-images) to
`24.04`


</details>



🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't
swamp any CI resources or overwhelm the project. See docs for
`prhourlylimit` for details.


---

❓ Got questions? Check out Renovate's
[Docs](https://docs.renovatebot.com/), particularly the Getting Started
section.
If you need any further assistance then you can also [request help
here](https://redirect.github.com/renovatebot/renovate/discussions).


---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/bazel-contrib/rules_fuzzing).


<!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Based on https://github.com/bazel-contrib/rules-template

The release job creates an archive with the `v`-prefixed tag in the
name, which caused the publish job to fail as it expected the name
without the `v`.


https://github.com/bazel-contrib/rules_fuzzing/actions/runs/16354558276/job/46210158348#step:6:24

Add a strip_prefix to fix
https://github.com/bazel-contrib/rules_fuzzing/actions/runs/16363893709/job/46237275734#step:6:25.

The linters aren't pinned and thus can start to fail on commits that
don't touch any files they apply to.

Also don't run all workflows twice for a PR.