After yarn release minor version doesn't increase

[santyas]

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

• npx create-next-app@latest --typescript
• commit-and-tag-version 10.0.1
  @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.

[santyas]

Well, if it starts from 1.0.0 works! But the commit message keep printing 'chore(release): 1.1.1'

[TimothyJones]

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?

[santyas]

@TimothyJones Excellent, I will start an example with 1.0.0. Thanks.

Second thing, nevermind. It's possible to custimize it from .versionrc

[TimothyJones]

See also this comment: #26 (comment)