-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set Major. Minor, or Patch Release #188
Comments
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
HTH |
The same question: I had the following tags:
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. |
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.
The text was updated successfully, but these errors were encountered: