chore(renovate): restore CRS v4 cooldown exemption - #535
Conversation
PR #525 added `minimumReleaseAge: "0 days"` to the `coreruleset-v3` and `coreruleset-v4` package rules, so that first-party CRS releases are not held back by the 7-day supply-chain cooldown in coreruleset/renovate-config. PR #526 branched before #525 landed, and its merge (b6daec8) kept the v3 exemption while dropping the v4 one. The regression went unnoticed because v3 and v4-lts still flow through immediately; only the flagship v4 version the site advertises as current has been waiting a week and needing a manual tick on the dependency dashboard. This restores the rule to what #525 merged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Renovate configuration now sets ChangesCRS v4 Renovate updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized configuration change restores the intended cooldown exemption for the current CRS release; no actionable merge-blocking risk remains after normal checks and review. 🚥 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 |
what
Adds
minimumReleaseAge: "0 days"back to thecoreruleset-v4package rule inrenovate.json.why
This is a regression, not a new policy decision.
#525 added the exemption to both
coreruleset-v3andcoreruleset-v4, so that first-party CRSreleases are not held back by the 7-day supply-chain cooldown that
coreruleset/renovate-configapplies to everything:
#526 branched before #525 landed, and its merge commit b6daec8 kept the v3 exemption while dropping
the v4 one. Current
maintherefore exemptscoreruleset-v3andcoreruleset-v4-ltsbut notcoreruleset-v4— so the version the site advertises as the current release is the only one thatwaits a week and has to be ticked by hand on the dependency dashboard.
That is what is happening in #53 right now:
coreruleset-v4→v4.29.0sat under Pending StatusChecks because 4.29.0 was published today, while the v3 and LTS entries were free to flow through.
references
coreruleset-v4rule as merged in chore(renovate): exempt CRS releases from cooldown; rename version keys #525Validated with
renovate-config-validator. Formatting left as-is:renovate.jsondoes not currentlysatisfy the repo's Prettier version, and Prettier is not run in CI, so reformatting would have
enlarged the diff for no gain.
Summary by CodeRabbit
coreruleset-v4can now be adopted immediately without a release-age delay.