From 3f976754fe9d0b84add6ac191b96ebdd249e3371 Mon Sep 17 00:00:00 2001 From: fi3ework Date: Tue, 25 Aug 2026 15:53:55 +0800 Subject: [PATCH] chore: let the rstack toolchain group own its release-age cooldown MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The shared security preset's cooldown waiver list does not cover `@rstackjs/**` and `rstack`, so those updates were held back a day while the rest of the group updated immediately — splitting one toolchain release into two branch updates and two CI rounds. Set `minimumReleaseAge: null` on the group so the whole toolchain updates as soon as a release ships, independent of the preset's list. --- .github/renovate.json5 | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.github/renovate.json5 b/.github/renovate.json5 index ff31e39..046fd99 100644 --- a/.github/renovate.json5 +++ b/.github/renovate.json5 @@ -26,9 +26,11 @@ // The Rstack toolchain is what this repo exists to support and it ships // every few days, so it opts out of the weekly window entirely: a PR is // opened on the next run after a release. `schedule:weekly` still governs - // everything else, and `github>rstackjs/renovate:security` already waives - // the release-age cooldown for the same set. Listed after `all-patch` so - // these land in their own PR instead of the weekly patch roll-up. + // everything else. This group owns its cooldown policy end-to-end: + // `minimumReleaseAge: null` waives the security preset's 1-day cooldown + // for every package listed here, rather than relying on the preset's own + // waiver list staying in sync. Listed after `all-patch` so these land in + // their own PR instead of the weekly patch roll-up. // // This includes `@rslint/core`, `@rstest/core` and `rstack`, whose ranges // sit alongside the runtime `SUPPORT_MATRIX` (shared/versionCheck.ts). @@ -50,6 +52,7 @@ 'rstack', ], schedule: ['at any time'], + minimumReleaseAge: null, }, ], }