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
BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
However, I can't figure out how to use this in cz bump. It looks like I can use only the type to drive the version number changes. Example pyproject.toml config:
As far as I can tell, bump_map read only the first match. So even if I specify feat!, it doesn't pick it up. The same goes for the BREAKING CHANGE footer.
Is this way of specifying breaking changes even supported or would I have to diverge from the standard and use a breaking kind of type instead?
I read through the entire documentation, searched existing issues and discussions and was not able to find any answers.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello 👋
The conventional commit message format allows for different ways of specifying breaking changes:
However, I can't figure out how to use this in
cz bump
. It looks like I can use only thetype
to drive the version number changes. Examplepyproject.toml
config:As far as I can tell,
bump_map
read only the first match. So even if I specifyfeat!
, it doesn't pick it up. The same goes for theBREAKING CHANGE
footer.Is this way of specifying breaking changes even supported or would I have to diverge from the standard and use a
breaking
kind of type instead?I read through the entire documentation, searched existing issues and discussions and was not able to find any answers.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions