chore: let the rstack toolchain group own its release-age cooldown - #36
Merged
Conversation
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.
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
The
rstack toolchainRenovate group is meant to update as soon as a release ships (schedule: ['at any time']), but the shared security preset's cooldown waiver list does not cover@rstackjs/**andrstack— both in use here — so those updates were held back by the 1-dayminimumReleaseAgewhile the rest of the group updated immediately. One toolchain release could thus split into two branch updates and two CI rounds.Set
minimumReleaseAge: nullon the group so it owns its cooldown policy end-to-end, independent of the preset's waiver list, and reword the comment to state that intent (the old comment claimed the preset already waived the cooldown for the whole set, which was inaccurate).Validated with
renovate-config-validator;pnpm lintandpnpm test:unitpass.Related Links
None.
Checklist