Use Dependabot's default cooldown before merging fresh package releases
GitHub now waits three days before opening Dependabot version-update pull requests, reducing exposure to compromised or broken package releases.
The useful part
What you get from it
GitHub has changed Dependabot version updates so new package releases must sit in the registry for at least three days before Dependabot opens a version-update pull request. Security updates still open immediately.
Use this as a low-friction supply-chain safety check. The default gives maintainers and the wider ecosystem time to flag compromised, yanked, or broken releases before they land in routine dependency-update PRs.
What to do
- Leave the new default in place for most repositories.
- Keep security updates immediate; the cooldown applies to version updates, not urgent security fixes.
- Override the window in
.github/dependabot.ymlonly when your release process has a clear reason. - Watch high-risk ecosystems or critical services for packages that should use a longer cooldown.
Best fit
| Repository type | Suggested move | Caveat |
|---|---|---|
| Standard app repos | Keep the three-day default | Review lockfile-only bumps before merge |
| Security-sensitive services | Consider a longer cooldown for non-security updates | Do not delay patched security advisories |
| Fast-moving libraries | Tune per ecosystem in dependabot.yml | Document why the shorter window is acceptable |
Community
0Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign inNo comments yet. Start the discussion.