fix(renovate): normalize SHA-pin comments to major-version-only - #20
Merged
wgordon17 merged 1 commit intoJul 28, 2026
Merged
Conversation
Renovate's native github-actions manager writes major-only comments (e.g. "v7") when bumping the root workflow files, but the custom regex customManagers for the .jinja template sources resolved the full github-releases tag (e.g. "v7.0.0") for the same dependency -- same logical bump, two different comment formats, causing the consistency check to fail whenever the SHA-pin/flake-input comment in a template file diverges from its already-bumped root counterpart (seen on PR gordon-code#19). extractVersionTemplate normalizes both managers to the same major-only granularity going forward.
wgordon17
marked this pull request as ready for review
July 28, 2026 19:18
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
1 participant
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.
Summary
github-actionsmanager writes major-only version comments (e.g.v7) when bumping SHA-pinned actions in root workflow files, but the custom regex customManagers for the.jinjatemplate sources resolved the fullgithub-releasesrelease tag (e.g.v7.0.0) for the same dependency — causing theconsistencycheck to fail whenever a template's SHA-pin/flake-input comment diverges from its already-bumped root counterpart (seen on PR chore(deps): update dependency actions/checkout to v7 #19)extractVersionTemplate: "^(?<version>v\\d+)"to both the SHA-pinned-actions and Nix-flake-input customManagers so they normalize to the same major-only granularity as the native manager going forward.github/renovate.jsonvalidates cleanly against the fleet's actual pinned Renovate version (43.150.0)