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
I also had the same issue when I tried to commit a perf commit with BREAKING CHANGE: in the body, I was expecting a major release but instead it triggers the patch.
Is there is any way to add multiple types with multiple release?
Or something to override the rules if it found the BREAKING CHANGE: word in the body of the commit message?
I had the same issue like you.
But I found a solution by adding {breaking: true, release: 'major'} on my releaseRules
We’re using the
conventionalcommits
preset. In this preset, adding an exclamation after the type triggers a breaking change/major version bump.Using the default
releaseRules
this works.feat!:
,fix!:
andperf!:
are recognized as major/breaking changes.In fact, anything with an exclamation triggers a major/breaking change, such as
docs!:
or evenallGloryToTheHypnoToad!:
Now we want to add
refactor
as a type.After adding this,
refactor:
triggers apatch
change, as expected.But
refactor!:
no longer triggers a major version bump.How do we get this to work?
Edit to add version info:
semantic-release 19.0.5
,@semantic-release/commit-analyzer 9.0.2
, Node 16.19.0The text was updated successfully, but these errors were encountered: