chore(renovate): give the ubuntu digest its own PR with a one-day soak - #14
Merged
Merged
Conversation
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.
Why
#9 has been open since 26 July and its branch was force-pushed 10 times. Only two of those were Ubuntu: the
24.04digest moved on 4 Aug and 19 Aug. The rest were action releases moving the pins (docker/login-action twice in late July, docker/setup-buildx-action on 19 Aug), two retitles from config changes, and rebases. Because the shared config batchespinanddigestupdates into one group, every one of those rewrote the same branch under the reviewer.What changes
A repo-level package rule puts the
ubuntudigest update into its own group (renovate/ubuntu-digest) withminimumReleaseAge: 1 dayinstead of the shared 5 days.24.04digest every two to four weeks. On its own, the PR only changes when Ubuntu does. The Actions pins stay in the shared group and stop moving once chore(deps): pin dependencies #9 (or its replacement) is merged, because pinned versions then flow asminor/patchwith the normal soak..1respins never made it to Hub in the last year), the Dockerfiledist-upgrades on top of it, and the PR still builds in CI and gets a human merge.:latest.After merging
Renovate will close #9 and open two PRs in its place: one for the Actions pins, one for the Ubuntu digest. Both will be green; merge the pins one first so the pin churn stops.