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
Below version 1, semver has no definition for what the version number means. I can't see any breaking changes in the screenshot you linked - but I think the behaviour is for the minor version to increase on breaking changes, and for patch versions to increase for everything else.
From version 1.0.0 onwards, semver should apply and you should see the version number increasing correctly.
But the commit message keep printing 'chore(release): 1.1.1'
I'm not sure what you mean by this - that looks right to me. Can you give more details on your setup and what you're expecting?
Hello!
Im trying to increase my changelog with my conventional commits.
Configured from: https://commitlint.js.org/#/guides-local-setup?id=install-commitlint
Always increase last numbers 0.1.XX
I want to get X.X.XX
Environment
@commitlint/cli
@commitlint/config-conventional
husky
The commit message after yarn release is always the same: chore release and 0.1.xx... It doesn't matter if you commit a feat or breaking change.
The text was updated successfully, but these errors were encountered: