Repository navigation
chore: automerge digest updates regardless of datasource - #152
Merged
Merged
Conversation
The two automerge rules gate on matchCurrentVersion and on a docker or npm datasource, and three open PRs sit green because they match neither. The distroless bases are pinned by digest with no tag, so Renovate extracts a currentDigest and no currentValue for matchCurrentVersion to test. The kobo-book-downloader ref comes from the custom manager with a git-refs datasource, which is outside matchDatasources. A digest bump has no version to gate on in the first place, so match it on update type alone. This automerges nothing the 0.x rule was not already letting through. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
Five Renovate PRs are open and green. Two are major updates held for review by design (#147, #114). The other three are never marked automergeable, and the debug log ends with
automerge: falsefor every branch.Both automerge rules gate on
matchCurrentVersionand on adockerornpmdatasource, and the three stuck PRs match neither:FROM gcr.io/distroless/static-debian13@sha256:...). Renovate extracts acurrentDigestand nocurrentValue, somatchCurrentVersionhas nothing to test. The log line isgetDigest(https://gcr.io, distroless/static-debian13, undefined). Tagging the image would not help, since the distroless tags are not numeric either.git-refsfrom the custom manager, outsidematchDatasources.What
One rule matching
digeston update type alone. A digest bump has no version to gate on in the first place, and this lets nothing through that the 0.x rule was not already automerging.🤖 Generated with Claude Code