Configure Renovate

[renovate]

Welcome to 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.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 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.

---

Detected Package Files

• MODULE.bazel (bazel-module)
• example/MODULE.bazel (bazel-module)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/publish.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• example/go.mod (gomod)

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.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title

---

What to Expect

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

Update dependency hermetic_launcher to v0.0.8

• Schedule: ["at any time"]
• Branch name: renovate/hermetic_launcher-0.x
• Merge into: main
• Upgrade hermetic_launcher to 0.0.8

Update bazel-contrib/.github action to v7.5.0

• Schedule: ["at any time"]
• Branch name: renovate/bazel-contrib-.github-7.x
• Merge into: main
• Upgrade bazel-contrib/.github to v7.5.0

Update dependency bazel_features to v1.47.0

• Schedule: ["at any time"]
• Branch name: renovate/bazel_features-1.x
• Merge into: main
• Upgrade bazel_features to 1.47.0

Update dependency bazel_skylib to v1.9.0

• Schedule: ["at any time"]
• Branch name: renovate/bazel_skylib-1.x
• Merge into: main
• Upgrade bazel_skylib to 1.9.0

Update dependency gazelle to v0.51.0

• Schedule: ["at any time"]
• Branch name: renovate/gazelle-0.x
• Merge into: main
• Upgrade gazelle to 0.51.0

Update actions/checkout action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: main
• Upgrade actions/checkout to v6

🚸 PR 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, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[malt3]

I don't think renovate makes sense here. We don't want to upgrade our bzlmod deps unless there's a very good reason for that.

[renovate]

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.