Skip to content

Apply the three-day release age to every Renovate update - #238

Merged
squarepots merged 1 commit into
mainfrom
chore/renovate-release-age
Oct 28, 2026
Merged

squarepots merged 1 commit into
mainfrom
chore/renovate-release-age

Conversation

@squarepots

@squarepots squarepots commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Part of #110.

What changed

  • .github/renovate.jsonc: minimumReleaseAge: "3 days" and internalChecksFilter: "strict" move from an npm-only package rule to the top level, so Cargo crates and GitHub Actions wait three days too. Security remediation keeps minimumReleaseAge: null under vulnerabilityAlerts and still opens immediately.
  • docs/testing.md states 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

  • The file still parses as JSON. Both options are standard top-level Renovate options. Renovate reports a config error on the dashboard if it rejects them.
  • No workflow or source change.

@squarepots
squarepots enabled auto-merge (squash) October 28, 2026 16:43
@squarepots
squarepots merged commit ec38298 into main Oct 28, 2026
12 checks passed
@squarepots
squarepots deleted the chore/renovate-release-age branch October 28, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant