Bump does not work properly

[o4rz3l]

Describe the bug

Bump does not reliably bump the version e.g. for a minor change ( feat: ) .In addition sometimes it produces "null" as next version (but i have not found a way to reproduce it).

BTW Just an idea: git cliff --bump --unreleased should offer to create the tag "v0.0.1" if no tag is set before.
To reproduce

Expected behavior

It should be bumped to 0.1.0.

Screenshots / Logs

Software information

• Operating system: Win10 as well as WSL2
• Project version: git-cliff 1.4.0

[welcome]

Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️

[orhun]

Hello, thanks for reporting this!

git cliff --bump --unreleased should offer to create the tag "v0.0.1" if no tag is set before.

Created #344

It should be bumped to 0.1.0.

Not sure what happened there, maybe ping @MarcoIeni who is the author of next_version.

[MarcoIeni]

It should be bumped to 0.1.0.

This is not how the next_version library works. I clarified it in MarcoIeni/release-plz#1064

Just an idea: git cliff --bump --unreleased should offer to create the tag "v0.0.1" if no tag is set before.

In rust, cargo new defaults to 0.1.0. Just FYI, it's up to Orhun to pick the right default!

[orhun]

I think this behavior is fine as long as it is documented in git-cliff as well, does anyone volunteer to add that?

[orhun]

The behavior has changed to support this use case in 4eef684