Repository navigation
feat(semantic-release): honor ! in commit titles via conventionalcommits preset - #252
Merged
Merged
Conversation
…mmits preset Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
commit: |
|
🎉 This PR is included in version 27.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
The semantic-release preset now uses the
conventionalcommitspreset for the commit analyzer and release notes generator. The defaultangularpreset ignores the!infeat(scope)!:, so a breaking PR without aBREAKING CHANGE:footer released nothing (see peerigon/glaskugel#1205). Addsconventional-changelog-conventionalcommits@^9.3.1(v10 needs a newer changelog writer than@semantic-release/release-notes-generatorbundles and crashes). Release notes change slightly: breaking changes are listed first and include!commits, and section order and version header differ.ai/rules.mdcnow recommends!plus aBREAKING CHANGE:footer, and the semantic-release README documents the differences.🤖 Generated with Claude Code