Describe the bug
If I tag dev-Versions, the calculation of rc-Versions is broken.
Let's assume the following git history:
HEAD
| fix
| v1.2.0-dev.0
| feat
| v1.1.0
...
If I now want to release a release candidate, I expect to get v1.2.0-rc.0, but I get v1.1.1-rc.0.
Environment
commit-and-tag-version version(s): 13.1.0
- Node/npm version: Node 22.23.1/npm 12.0.1]
- OS: Arch Linux
Additional context
After a bit of research, I can conclude, that the bug is caused by a mismatch:
- commit-and-tag-version seems to supply the version of the last full release (v1.1.0 in my example)
- conventional-recommended-bump 12.1.0 seems to check all commits since the last semver tag (v.1.2.0-dev.0 in my example)
Describe the bug
If I tag dev-Versions, the calculation of rc-Versions is broken.
Let's assume the following git history:
HEAD
| fix
| v1.2.0-dev.0
| feat
| v1.1.0
...
If I now want to release a release candidate, I expect to get v1.2.0-rc.0, but I get v1.1.1-rc.0.
Environment
commit-and-tag-versionversion(s): 13.1.0Additional context
After a bit of research, I can conclude, that the bug is caused by a mismatch: