Set Major. Minor, or Patch Release

[justperbox]

Dear all,

I recently integrated this with my project.
This project already has manual releases and tags.
the latest one is v.1.12.0

How do I continue the sequence when using this action?
Can i force it to use v.1.13.0 on the next run?

Please help.

Thank you in advance.

[grudelsud]

I landed here for the same reason

@justperbox from what I've seen so far, it reads existing existing tags (last 100 by default) and bumps the value of the last available version accordingly. Preconditions are that

1. existing tags are in semver format (so in your case, you have an extra dot: rename your tag from v.1.12.0 to v1.12.0 and the magic should happen)
2. commits are spelled out in "conventional commits" format, i.e.: https://www.conventionalcommits.org/en/v1.0.0/

HTH

[vitalyk-multinarity]

The same question: I had the following tags:

git tag --sort=committerdate
v0.0.1.0
v0.0.1.1
v0.0.2.0

but the new tag was "v0.0.1-cicd-testing-semver-7-11-2023.0".

In general, I'm not interesting in using "conventional commits", I just want to bump 'patch' or 'release' number according to the flow.