ci: use the conventionalcommits preset so breaking changes are released - #26
Merged
Merged
Conversation
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.
With the default (angular) preset semantic-release doesn't understand
!after the type: a PR titledfeat!: …orrefactor!: …(without aBREAKING CHANGE:footer) resulted in no release at all, while the README says it results in a major release.Changes
.releaserc.json: the commit analyzer and the release-notes generator use theconventionalcommitspreset.semantic-release.yml: installconventional-changelog-conventionalcommits@9via the action'sextra_plugins. Version 10 needs a newer changelog writer than the release-notes generator bundled with semantic-release 25 and fails when generating the release notes.!after any type → major;perf:results in a patch release (it was listed as "no release");revert:→ no release.Tested locally
feat!:/refactor!:→ major,BREAKING CHANGE:footer → major,feat:→ minor,fix:/perf:→ patch,docs:/chore:/ci:/build:/refactor:/test:/style:/revert:→ no release. With the current configfeat!:→ no release.semantic-release@25 --dry-runwith this config (on refactor!: remove unused create_zip prepare-assignment/toolbox#16): "The next release version is 1.0.0", release notes with a "⚠ BREAKING CHANGES" section.A
ci:title doesn't trigger a release.