Repository navigation
Apply the three-day release age to every Renovate update - #238
Merged
Merged
Conversation
squarepots
enabled auto-merge (squash)
October 28, 2026 16:43
This was referenced Oct 31, 2026
Merged
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
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.
Part of #110.
What changed
.github/renovate.jsonc:minimumReleaseAge: "3 days"andinternalChecksFilter: "strict"move from an npm-only package rule to the top level, so Cargo crates and GitHub Actions wait three days too. Security remediation keepsminimumReleaseAge: nullundervulnerabilityAlertsand still opens immediately.docs/testing.mdstates the rule for both Renovate and hand-recreated updates.Why
#236 already held back Cargo releases younger than three days by hand, including the 2026-10-28 Tauri plugin releases, whose Rust and npm halves Renovate groups together. With the age rule on npm only, approving the Tauri group would open a branch for the Rust half at once while the npm half still waits. The repository now applies one rule to every routine update instead of the reviewer remembering it for Cargo.
Validation