Uh oh!
There was an error while loading. Please reload this page.
fix!: support exclamation mark in conventional commits - #1105
Merged
vbreuss merged 1 commit intoMar 17, 2024
Conversation
vbreuss
enabled auto-merge (squash)
March 17, 2024 13:57
vbreuss
deleted the
topic/support-exclamation-mark-in-conventional-commits
branch
March 17, 2024 14:00
This is addressed in release v21.0.2. |
This was referenced Jun 25, 2026
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 freeto 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.
According to conventional commits breaking changes could be indicated via an exclamation mark (e.g.
feat!:orfix!:).Adapt the build pipeline, so that also breaking changes are deployed.