Conversation
Projects repeatedly hit the same two problems when adopting Dependabot: security updates are opened individually and ungrouped by default, so a repository accumulates a pile of open PRs, and a freshly published version can be pulled in before a compromised or typosquatted release has been yanked. Add a guideline that walks through a dependabot.yml addressing both. It groups every ecosystem's version and security updates into a single PR per run, and sets a 30-day cooldown that delays version updates only, so advisory-driven security fixes still arrive immediately. Entries are included for npm, GitHub Actions, Docker, Go modules, and cargo, along with a note that target-branch takes no wildcards and release branches therefore need duplicated entries. The complete file is reproduced verbatim at the end so it can be copied directly into .github/dependabot.yml. Link the new page from the Security section of the project best practices and add it to the Guidelines nav. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Ry Jones <ry@linux.com>
ryjones
marked this pull request as ready for review
August 31, 2026 20:20
ryjones
requested review from
EnriqueL8,
OsamaRab3,
VRamakrishna,
arsulegai,
dmueller2001,
hendrikebbers,
kkaur01,
kmillikin,
matthew1001,
mbrandenburger and
tock-ibm
as code owners
August 31, 2026 20:20
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.
Projects repeatedly hit the same two problems when adopting Dependabot: security updates are opened individually and ungrouped by default, so a repository accumulates a pile of open PRs, and a freshly published version can be pulled in before a compromised or typosquatted release has been yanked.
Add a guideline that walks through a dependabot.yml addressing both. It groups every ecosystem's version and security updates into a single PR per run, and sets a 30-day cooldown that delays version updates only, so advisory-driven security fixes still arrive immediately. Entries are included for npm, GitHub Actions, Docker, Go modules, and cargo, along with a note that target-branch takes no wildcards and release branches therefore need duplicated entries.
The complete file is reproduced verbatim at the end so it can be copied directly into .github/dependabot.yml.
Link the new page from the Security section of the project best practices and add it to the Guidelines nav.