GitHub Blog
Read post

Tame Dependabot: Group your updates, slow the cadence, keep security fast

Dependabot's default configuration can flood repositories with individual pull requests for every dependency update. Using Microsoft's GCToolkit as a real-world example, this post shows how three changes to dependabot.yml dramatically reduce noise: grouping all updates into a single batched pull request per ecosystem using a wildcard pattern, slowing the check interval from daily to monthly, and ensuring every package ecosystem (not just github-actions) is covered. Critically, security updates remain unaffected by these changes — they still fire immediately upon vulnerability disclosure. A new default three-day cooldown period also now delays version-update PRs automatically, providing a buffer against supply chain attacks via freshly published malicious packages. The post includes actionable YAML examples and tips for monorepos using the directories key with group-by: dependency-name.

    #security#github-actions#maven#dependabot
Jul 29•10m read time•From github.blog
Post cover image
Table of contents
The problem: Good defaults, wrong cadenceThe fix: Three changes that compoundBut what about security updates?A new safety net: default package cooldownHow to apply this to your own repositoriesThe takeawayTags:Written by
12 Impressions
GitHub Blog's image
GitHub Blog

The GitHub Blog provides updates, announcements, and insights from the world's leading software deve...

1.4K Followers

•

3K Upvotes

Would you recommend this post?

Copy link
WhatsApp
Facebook
X
New Squad
  • © 2026 Daily Dev Ltd.
  • Guidelines
  • Explore
  • Tags
  • Sources
  • Squads
  • Leaderboard