chore: remove Dependabot in favour of Renovate#13
Merged
Conversation
Both Dependabot and Renovate were updating Docker and GitHub Actions dependencies, producing duplicate PRs. Renovate provides the same coverage with better grouping, SHA pinning, and automerge control, so Dependabot is removed. The dependency-review and scorecards workflows are unaffected — they scan for vulnerabilities and score supply-chain posture independently of which updater is in use.
Aligns the three workflows to the same actions/checkout SHA (de0fac2e4500dabe0009e67214ff5f5447ce83dd) so Renovate can update them as a single grouped PR going forward.
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
1 participant
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.
Summary
.github/dependabot.yml— eliminates duplicate update PRs with Renovateactions/checkoutto v6.0.2 (de0fac2e...) across all three workflows — resolves the version mismatch betweendevcontainer-ci.yml(was v4.2.2) and the other two (were v4.3.1)Why remove Dependabot
Both Dependabot and Renovate were tracking Docker and GitHub Actions updates, producing duplicate PRs for the same changes. Renovate is kept because it provides SHA digest pinning, grouped updates, automerge policies, and granular scheduling that Dependabot does not.
The
dependency-reviewandscorecardsworkflows are unaffected — they scan for vulnerabilities and score supply-chain posture independently of which updater is in use.Why align actions/checkout
With all three workflows on the same SHA, Renovate will batch future updates into a single grouped PR (per the
groupName: "GitHub Actions"rule inrenovate.json) instead of opening separate PRs per workflow.