chore: label all image build input updates as image - #377
Merged
Conversation
The "Image Builds" rule set both the group and the `image` semantic commit type, but was scoped to patch and digest updates. Minor and major updates to `build.yaml` therefore fell back to the `:semanticCommitTypeAll(chore)` preset and opened as `chore(deps): ...` even though they ship a new image. Split the rule in two so the commit type applies to every `build.yaml` update while grouping stays limited to patch and digest updates, which keeps minor and major updates in their own pull requests. 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
2 participants
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
Split the
Image BuildsRenovate rule into two: one that applies theimagesemantic commit type to every**/build.yamlupdate, and one that keeps the group limited topatchanddigestupdates.Why
The single rule set both
groupNameandsemanticCommitType: image, but was scoped bymatchUpdateTypes: ["patch", "digest"]. Minor and majorbuild.yamlupdates never matched it, so they fell back to the:semanticCommitTypeAll(chore)preset and opened aschore(deps): ...despite shipping a new image:terraform/build.yaml1.15.9→1.16.0node/build.yaml26.7.0→26.8.1Simply dropping
matchUpdateTypeswould have folded minor and major updates into theImage Buildsgroup as well, batching unrelated runtime bumps into one pull request. Keeping the grouping rule separate preserves the current batching behaviour while fixing the commit type.Verification
renovate-config-validator→INFO: Config validated successfullyGenerated by Claude Code