chore(deps): group Dependabot security updates to cut PR noise#756
Merged
Conversation
Security-updates (GHSA-driven) bypass grouping by default, so each advisory opens its own PR — four landed the same day (cryptography, tornado, bleach, jupyter-server). Add an `applies-to: security-updates` group per ecosystem so a burst of advisories batches into a single PR instead of one per package. The existing version-update groups now carry an explicit `applies-to: version-updates`, required once a second group exists in the block. Security PRs stay advisory-timed: cooldown and the monthly schedule apply only to version-updates, by design — grouping only collapses the count, it does not delay or auto-merge CVE fixes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
Adds an
applies-to: security-updatesgroup to each ecosystem in.github/dependabot.ymlso a burst of security advisories batches into one PR per ecosystem instead of one PR per package.Why
The version-update side of our Dependabot config already works well — monthly schedule, 14-day cooldown, grouped minor/patch into a single PR. But Dependabot's security-updates channel (GHSA-driven) bypasses grouping, cooldown, and the schedule by default. So four security PRs landed the same day (cryptography, tornado, bleach, jupyter-server) — exactly the noise this change removes.
By default a
groupsblock only applies to version-updates, so security PRs were never grouped. This adds a paired security group per ecosystem (and makes the existing groups'applies-to: version-updatesexplicit, which is required once a second group exists).What this does not change
Security PRs stay advisory-timed — cooldown and the monthly schedule apply only to version-updates, by design (fix CVEs fast). Grouping only collapses the count; it does not delay or auto-merge CVE fixes. No auto-merge is introduced anywhere.
— Claude on behalf of Cail
🤖 Generated with Claude Code