chore(deps): skip the Dependabot cooldown for packages this org publishes - #484
Conversation
…shes Since 2026-07-14 Dependabot waits 3 days after a release before proposing a version update. cpp-linter 1.14.0 reached PyPI on 2026-09-13 and every job since logged "Filtered out 1 versions due to cooldown". The delay is meant for third-party releases; cpp-linter and clang-tools are published by this org, so exclude them and keep the 3-day default for everything else.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe Dependabot ChangesDependabot cooldown
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The Dependabot configuration matches the intended cooldown and package exclusions, with no identified merge-blocking risk. 🚥 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 |
|
I will wait for Dependabot to bump cpp-linter to the latest version, but I have to wait for 3 days by default. So I would like to think about excluding our published package from the cooldown section. |
Why
Since 2026-07-14 Dependabot applies a 3-day cooldown to version updates by default (changelog). cpp-linter 1.14.0 reached PyPI on 2026-09-13 22:05 UTC; the uv jobs on 09-13, 09-14 and 09-15 all logged
Filtered out 1 versions due to cooldownfor it and left the pin at 1.13.0.The cooldown exists to give third-party releases time to be vetted.
cpp-linterandclang-toolsare published by this org, so the wait only delays our own release train.What
cooldownon the uv ecosystem withdefault-days: 3(the platform default, now explicit) andexclude: [cpp-linter, clang-tools].excludetakes precedence, so those two update on the next run after a release; everything else keeps the 3-day wait (options reference).Merging triggers a Dependabot run; it should open the 1.13.0 → 1.14.0 bump in the
orggroup right away.Summary by CodeRabbit