Dependabot version updates introduce default package cooldown

Hacker News Top Tools

Summary

Dependabot now waits three days before opening version update PRs to reduce risk of supply chain attacks. Security updates remain immediate.

No content available
Original Article
View Cached Full Text

Cached at: 07/14/26, 10:19 PM

# Dependabot version updates introduce default package cooldown Source: [https://github.blog/changelog/2026-07-14-dependabot-version-updates-introduce-default-package-cooldown/](https://github.blog/changelog/2026-07-14-dependabot-version-updates-introduce-default-package-cooldown/) Dependabot now waits until a new release has been available on its registry for at least three days before opening a version update pull request\. This cooldown is now the default and requires no configuration\. New releases are a common entry point for supply chain attacks where a compromised or broken version can reach your dependency updates before maintainers and the community have caught it\. A short delay gives that signal time to surface, so you are less likely to merge a bad release the moment it ships\. A few things to know: - The default applies only to version updates\. Security updates still open immediately, so critical fixes are never delayed\. - You stay in control\. Use the`cooldown`option in your`\.github/dependabot\.yml`to set a different window or opt out entirely\. This default applies to Dependabot version updates across all supported ecosystems on github\.com and will take effect in GitHub Enterprise Server \(GHES\) 3\.23\. Learn more in[our docs about Dependabot cooldowns](https://docs.github.com/code-security/dependabot/working-with-dependabot/dependabot-options-reference#cooldown-)\.

Similar Articles

Quoting GitHub Changeling

Simon Willison's Blog

GitHub's Dependabot now defaults to a three-day cooldown before opening version update pull requests, requiring no configuration.

Quoting Seth Larson

Simon Willison's Blog

PyPI now rejects uploads of new files to releases older than 14 days to prevent supply-chain attacks, a proactive security measure announced by Seth Larson.

Upcoming breaking changes for NPM v12

Hacker News Top

npm v12 introduces security-related breaking changes to npm install that disable automatic execution of scripts, git dependencies, and remote URL dependencies by default. Users can prepare by upgrading to npm 11.16.0+ and reviewing warnings to explicitly opt into trusted behaviors.

Cooldown Support for Ruby Bundler

Hacker News Top

Bundler 4.0.13 introduces a cooldown feature that blocks resolution to gems published less than N days ago, mitigating supply-chain attacks. It is opt-in and configurable per source, setting, or command-line flag.