chore(deps): drop dependabot version updates, keep security only - #511
Merged
Conversation
The github-actions block I added in #499 had no groups, so each of the five actions in the tree opened its own PR and then hit the default limit of 5. Group them into one, and cap the limit at 2. The npm block had the same hole for majors: its groups only covered minor and patch, so any major would have gone out as a standalone PR per package. Added a majors group, separate from the minor/patch ones so a major bump still lands somewhere reviewable on its own.
Reverts the dependabot.yml added in #499. That file turned on *version* updates for every dependency, and the first weekly run opened 15 PRs: five ungrouped actions bumps and ten majors. Grouping would have cut it to three or four a week, which is still noise nobody asked for. Security patching does not need this file. Dependabot alerts and the automated-security-fixes repo setting both work with no config, and those are what actually get CVEs fixed. Version updates were scope I added on my own; removing them puts it back to the original ask. Deleted rather than emptied: `updates: []` fails Dependabot's schema and would show up as a config error on every run.
Anton-Horn
changed the title
Anton-Horn
enabled auto-merge
July 22, 2026 13:18
This was referenced Jul 22, 2026
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.
Reverts the
dependabot.ymlI added in #499.That file turned on version updates for every dependency. The first weekly run opened 15 PRs: five ungrouped actions bumps (#501-#505) and ten majors (#507-#517). My first attempt here was to group them, but that only gets it to three or four PRs a week, which is still noise nobody asked for.
Security patching does not need this file. Dependabot alerts and the automated-security-fixes repo setting both work with no config at all, and those are what actually get CVEs fixed. Routine version bumps were scope I added on my own initiative; removing them puts things back to the original ask.
Deleted rather than emptied, because
updates: []fails Dependabot's schema and would surface as a config error on every run.The CodeQL workflow from #499 stays. That one is doing real work.
Closing #501-#517 once this lands.