Repository navigation
ci: note that Dependabot security PRs skip the release-age cooldown - #7
Merged
Merged
Conversation
The dependabot.yml header said cooldown does not delay security PRs, but not that pnpm's minimumReleaseAge does not either: since dependabot-core#15170, Dependabot runs pnpm with --config.minimumReleaseAge=0 for security updates. It also read as if security updates were already on; they open PRs only once enabled in the repo's code security settings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TkHa1BVnm277qEiEuipG6n
|
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
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.
Summary
Corrects the header comment of
.github/dependabot.yml, added in the dependency-security PR. It saidcooldowndoes not delay security PRs, but it did not say that pnpm'sminimumReleaseAgedoes not guard them either. Since dependabot-core#15170, merged on 2026-05-29, Dependabot runs pnpm with--config.minimumReleaseAge=0for security updates, so a security PR can bring a version that is less than 24 h old.The comment also read as if security updates were already on. They open PRs only once they are enabled in the repo's code security settings, and today the org's "GitHub recommended" configuration leaves them
not_set.Changes
.github/dependabot.yml: comment only. The configuration itself is unchanged.Verification
zizmor==1.30.1 --offlineon.github/reports no findings.🤖 Generated with Claude Code
https://claude.ai/code/session_01TkHa1BVnm277qEiEuipG6n