feat(ci): derive auto-tag bump level from conventional commits#20
Merged
Conversation
Until now auto-tag always cut a patch release regardless of what landed on main. Now it parses commit subjects since the previous tag and picks the highest applicable bump: - `<type>(scope)?!:` subject OR `BREAKING CHANGE:` footer -> major - `feat(scope)?:` subject -> minor - anything else -> patch Workflow header, job name, README release section, and CONTRIBUTING commit-message guidance updated to match. Manual "Bump & Release" is still available for out-of-band releases.
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
Currently Auto-tag always cuts a patch release, regardless of what was merged. This PR teaches it to read commit subjects since the previous tag and pick the right bump level.
Bump rules (first match wins):
!before the:in the subject (feat!:,fix(scope)!:, …) or aBREAKING CHANGE:footer → majorfeat(...):commit → minorThe manual Bump & Release workflow is still available for out-of-band releases and for overriding the inferred level when needed.
Updated alongside:
README.mdrelease pipeline descriptionCONTRIBUTING.mdcommit-message section now points at Conventional Commits and explains the link to Auto-tagTest plan
.github/and docs, so Auto-tag'spathsfilter means no tag will be cut from the merge itself — good, lets us validate the logic on the next Sources-bearing commit.feat:,feat(scope):,fix!:,feat(scope)!:, bodies containingBREAKING CHANGE:).