Description

Running $ cz bump --prerelease beta when the current version is a previous pre-release bumps the version even when there are no commits that would require it, e.g. only build/ci commits.

Steps to reproduce

1. Start with a final version, e.g. v0.0.1
2. $ git commit -m "ci: CI-specific change not requiring release"
3. $ cz bump --prerelease beta -> Refuses to bump the version as expected
4. $ git commit -m "fix: Prospective fix requiring beta testing"
5. $ cz bump --prerelease beta -> Bumps to v0.0.2b0 as expected
6. $ git commit -m "build: Local devel change not requiring release"
7. $ cz bump --prerelease beta -> Bumps unexpectedly to v0.0.2b1

Current behavior

Maintainers can't use $ cz bump as a tool to interpret conventional commit messages to determine if a release is required when the current version is a pre-release. When some contributors are making build: .../ci: ... changes while features are in beta testing, this behavior results in a lot of noisy, meaningless v#.#.#b9999999.... bump commits, tags, and releases.

Desired behavior

Maintainers should be able to use $ cz bump, or $ cz ... in some other form, to determine if the conventional commit messages since the last pre-release require a new pre-release.

Environment

(build) rpatterson@rpatterson:~/src/devel/python-project-structure$ cz version --report
Commitizen Version: 2.42.1
Python Version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0]
Operating System: Linux