renovate: add update-soak windows; majors never automerge - #6
Merged
Conversation
Auto-merge previously fired the instant CI was green with zero minimumReleaseAge, so a yanked or hotfixed release could land unattended. Add soak windows: patch/digest 2 days (still automerge), minor 5 days, major 7 days. Split the combined minor+major rule so majors get an explicit automerge:false — a major is always human-reviewed regardless of CI. Update README's contract section to match.
1 task
Two behavior changes on top of the soak windows: - internalChecksFilter:none — Renovate's default (strict) suppresses a PR while the release is still within minimumReleaseAge, hiding it during the soak. With 'none' the PR is created immediately (pending stability check), so every update is visible and a human can manually merge early (e.g. a hotfix); the soak only gates AUTOMERGE. Also dropped the Monday schedule from minor/major so PRs aren't batched. - Minor updates now automerge after a 5-day soak + green CI (was manual). Contract updated: minor automerge raises the CI bar (runtime tests, not just build+lint); repos can override to disable. Added a Major-bump SOP section. Majors stay manual.
cewert
added a commit
to jellyrock/jellyrock
that referenced
this pull request
Jun 12, 2026
…r 5d Mirrors the org-preset update (jellyrock/.github#6): - internalChecksFilter:none so soaking PRs are created immediately and a hotfix can be merged manually early; the soak only gates automerge. - minor + patch/digest automerge after their soak + green CI. JellyRock's CI (on-device unit tests + RTA) clears the raised bar for minor automerge. sgRouter carve-out stays no-automerge.
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.
What
Adds update-soak windows to the org Renovate preset, makes PRs visible immediately while they soak, and tightens automerge by update type.
minimumReleaseAge)Why
Auto-merge previously fired the instant CI went green with zero minimum-release-age, so a yanked or hotfixed release could land unattended on
mainof any repo extending this default. A short soak lets the ecosystem surface a bad release before it merges, without stalling routine patches.Behavior details
internalChecksFilter: "none"— Renovate's default (strict) suppresses a PR while the release is still withinminimumReleaseAge, hiding it during the soak. Withnone, the PR is created immediately (with a pendingrenovate/stability-dayscheck), so every update is visible and a human can manually merge early (e.g. a hotfix). The soak only gates automerge. Dropped the Mondayschedulefrom minor/major so PRs aren't batched.Notes
renovate.jsonshort-term so it's covered before this preset propagates; that local duplicate will be removed once this is live.