Remove minimumReleaseAge check for digest updates - #316
Open
keremgocen wants to merge 1 commit into
Open
Conversation
| "packageRules": [ | ||
| { | ||
| "matchUpdateTypes": ["digest", "pinDigest"], | ||
| "minimumReleaseAge": null |
Contributor
There was a problem hiding this comment.
From the thread you sent this looks like a nicer option no? That way it uses the timestamp if it can find it
Suggested change
| "minimumReleaseAge": null | |
| "minimumReleaseAgeBehaviour": "timestamp-optional" |
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.
Eliminate the minimumReleaseAge requirement for digest and pinDigest updates in the configuration so the auto-merge can kick in once the PR is approved.
(see: renovatebot/renovate#39781 for the root cause, digest updates are usually missing the timestamp so our updates were left stale 14+ days until one of us merges them)