feat: route 0.x minor updates onto the major branches - #44
Merged
Conversation
Signed-off-by: Devin Buhl <devin@buhl.casa>
bo0tzz
approved these changes
Aug 5, 2026
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.
Renovate classifies
0.x → 0.yas a minor update even though SemVer gives 0.x releases no stability guarantee, so today a breaking zero-ver bump rides the same weekly grouped PR as genuinely safe minors and patches (typescript-projects,github-actions, ...). This adds one rule that setsadditionalBranchPrefix: "major-"for minors whose current version is 0.x, which lands them on the samemajor-<groupSlug>branch Renovate already uses to split grouped majors - so risky bumps get their own PR and the regular group PRs stay skimmable. Ungrouped 0.x minors just get amajor-branch rename.The devtools per-component tags are handled correctly:
versionCompatibilitystrips the<component>-prefix before version matching, soimage-build-action-v0.1.9is seen asv0.1.9and routed, whileuse-mise-action-v3.2.1is untouched. The only transition cost is a one-time regroup of open PRs that contain 0.x minors.