chore(dependabot): raise semver-patch cooldown to 5 days [skip ci] - #161
Conversation
Patch is the only update class that auto-merges with no human involved, yet carried the shortest cooldown (1 day, a third of GitHub's 3-day default). Soak time should scale with how little scrutiny a bump receives, not with how breaking semver claims it is. Costs nothing in security terms: cooldown never applies to Dependabot security updates, which still fire immediately. Propagated from simplify9/.github (dependabot-templates).
📝 WalkthroughSummary
Risk: Security-sensitive areas: Dependabot update timing. Security updates remain unaffected. Test coverage impact: No runtime code changes. No additional test coverage is expected. Operational concerns: Patch updates will be delayed by up to five days. Revert the configuration change if this delay causes unacceptable exposure or maintenance impact. WalkthroughDependabot patch-update cooldowns increase from 1 day to 5 days for npm, Docker, and GitHub Actions updates. ChangesDependabot cooldown configuration
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
chore(dependabot): raise semver-patch cooldown to 5 days
Patch is the only update class that auto-merges with no human
involved, yet carried the shortest cooldown (1 day, a third of
GitHub's 3-day default). Soak time should scale with how little
scrutiny a bump receives, not with how breaking semver claims it is.
Costs nothing in security terms: cooldown never applies to Dependabot
security updates, which still fire immediately.
Propagated from simplify9/.github (dependabot-templates).