ci: Allow exclamation mark alias to be used as BREAKING CHANGE keyword
#67
Conversation
This file contains 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
wakamsha
force-pushed
the
ci/enable-exclamation-mark-alias
branch
from
3b2c1d0
to
c4b37cc
Compare
wakamsha
changed the title
BREAKING CHANGE keyword
|
🎉 This PR is included in version 3.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Describe your changes
Allow
!to be used asBREAKING CHANGEsyntax in semantic-release.As mentioned in the comment below, I tried using
conventionalcommits, but didn't solve the problem:semantic-release/commit-analyzer#231 (comment)
As a workaround, I adopted the method mentioned in the comment below:
semantic-release/commit-analyzer#231 (comment)
Issue ticket number and link
Checklist before requesting a review