You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The conventionalcommits preset introduced an additional way to signal breaking with a ! after the type/scope.
For every other presets (and conventionalcommits when using the BREAKING CHANGE footer) the parsed object will have some values in commits.notes and that can be used to determine if the commit is a breaking change or not.
I see the case of a ! after type/scope is handled in the write:
The
conventionalcommits
preset introduced an additional way to signal breaking with a!
after the type/scope.For every other presets (and
conventionalcommits
when using theBREAKING CHANGE
footer) the parsed object will have some values incommits.notes
and that can be used to determine if the commit is a breaking change or not.I see the case of a
!
after type/scope is handled in the write:conventional-changelog/packages/conventional-changelog-conventionalcommits/writer-opts.js
Line 65 in 63d8cbe
I think the
addBangNotes
should also be called in the parser.The commit
feat!: Some breaking feature
currently parses to:but it should be instead parsed as:
or maybe:
The text was updated successfully, but these errors were encountered: