chore: one dependency bot, not two - #185
Merged
Merged
Conversation
This was the only repo in the org still running Dependabot. It owned the github-actions bumps while Renovate owned the chart pins, the Go module and the CI tool downloads — two tools splitting one job, in the one repo where the split was never revisited after Renovate arrived everywhere else. Renovate now owns all four. .github/dependabot.yml is deleted and github-actions joins the enabledManagers allowlist. This is not a like-for-like swap: the org preset sets pinDigests on github-actions, so actions are pinned to commit SHAs and kept there. Dependabot's config here did not do that, and SHA pinning is the reason those pins were brought up to date by hand in the first place — the tool now maintains what a person had to. The rest stays local, because it is genuinely local. enabledManagers is an allowlist rather than a default: this repo is a manifest catalog, and without it Renovate reads every values.yaml as a Helm chart it owns. The four custom managers that find chart pins inside ApplicationSet matrix elements have no equivalent anywhere else in the org. Both are described in the config rather than left to be inferred. The posture — patch and minor open a PR, majors labelled for review, CVE-triggered updates excluded from automerge twice over, related packages grouped — now comes from the shared preset instead of being absent here, which it was: this config carried no automerge rules and no vulnerability handling at all. CLAUDE.md said dependabot owned the actions. It now says what is true.
CI Results
All checks passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The situation
This was the only repo in the org still running Dependabot. It owned the github-actions bumps while Renovate owned the chart pins, the Go module and the CI tool downloads — two tools splitting one job, in the one repo where the split was never revisited after Renovate arrived everywhere else.
(Worth recording how I nearly got this wrong: an
gh api --jq '.name'sweep reported all 19 repos as having adependabot.yml. On a 404 body that expression emits the stringnull, which a-ntest reads as "present". Only this repo actually has one, and only this repo has Dependabot PRs.)The change
Renovate now owns all four managers.
.github/dependabot.ymlis deleted andgithub-actionsjoins theenabledManagersallowlist.This is not a like-for-like swap. The org preset sets
pinDigestson github-actions, so actions get pinned to commit SHAs and kept there. Dependabot's config here did not do that — and SHA pinning is exactly why those pins had to be brought up to date by hand earlier. The tool now maintains what a person had to.What stays local, and why
enabledManagersvalues.yamlas a Helm chart it ownsBoth of the first two are now described in the config itself rather than left to be inferred.
What the preset adds
Posture this config did not have at all: no automerge rules, no
vulnerabilityAlertsblock, no CVE packageRule, noosvVulnerabilityAlerts. It now gets patch/minor opening a PR, majors labelled for review, CVE-triggered updates excluded from automerge twice over, and OSV-based alerting on the Go module.Docs
CLAUDE.mdsaid Dependabot owned the actions bumps. It now says what is true.Verified
renovate-config-validator: valid, no migration neededtask validate: all validations pass — helm-render, kustomize builds, ApplicationSet schema, sync waves, dashboard gate, policy-admissionhttps://claude.ai/code/session_012iMnbboJuiUMSvu7n8oRhz