ci(release): default release-type to auto-derived bump#257
Merged
Conversation
The publish workflow required picking patch/minor/major on every release. The setup already runs @release-it/conventional-changelog, which can compute the bump from conventional commits, but the workflow always passed an explicit increment that overrode it. Add an 'auto' release-type (now the default): when selected, release-it runs without an increment and derives the bump from the commits since the last tag (feat -> minor, fix -> patch, BREAKING/! -> major). patch/minor/major remain as explicit overrides. Document the behavior and the squash-merge caveat that breaking changes must be marked with '!' in the PR title.
|
📦 Preview published for commit Install the preview with dist-tag: npm install @vc-shell/framework@pr-257Or pin to the exact commit: npm install @vc-shell/framework@2.1.0-pr257.a5b1627Published packages (dist-tag
|
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.
Overview
The publish workflow required manually picking
patch/minor/majoron everyrelease. The repo already runs
@release-it/conventional-changelog, which canderive the bump from conventional commits, but the workflow always passed an
explicit increment that overrode it.
Change
autorelease-type (now the default). Withauto, release-it runswithout an explicit increment and derives the bump from the commits since the
last tag:
BREAKING/!→ major,feat→ minor, otherwise patch.patch/minor/majorremain available as explicit overrides.RELEASING.md, including the squash-merge caveat:breaking changes must be marked with
!in the PR title, since the PR body'sBREAKING CHANGE:footer is dropped on squash.You still trigger the release manually — you just no longer pick the bump type.
Verification
publish.ymlis valid YAML.→
autoresolves to a minor).