Description
Description
commitizen-action cut a spurious patch release when we merged a ci
commit, ScribeMD/slack-templates@e2d9df0, to main
, because cz bump
incorrectly committed a bump. We made many ci
commits previously without encountering this issue, and I am not sure what was special about this case.
Steps to reproduce
-
Run
git clone git@github.com:ScribeMD/slack-templates
. -
Run
git checkout 0.6.17^
to checkout the commit that triggered the spurious release. -
Refer to our contributing guide if desired to maximize fidelity between our dev environments, but you can most likely get away with simply running commitizen 2.42.1.
-
Run
poetry run cz --no-raise 21 bump --yes --changelog --check-consistency --dry-run
. (Omit thepoetry run
portion if you didn't follow our contributing guide and installed commitizen some other way.) -
Observe the following output:
bump: version 0.6.16 → 0.6.17 tag to create: 0.6.17 increment detected: PATCH ## 0.6.17 (2023-04-05)
Current behavior
Here is the pertinent output from commitizen-action:
Commitizen version: 2.42.1
cz --no-raise 21 bump --yes --changelog --check-consistency
bump: version 0.6.16 → 0.6.17
tag to create: 0.6.17
increment detected: PATCH
Desired behavior
Commitizen shouldn't increment the version number when there are no feat
, fix
, or refactor
commits since the previous tag, 0.6.16 in this case.
Screenshots
No response
Environment
- Commitizen version: 2.42.1
- Python version: 3.11.2
- Operating system: Linux