Devrelease created after release-candidate doesn't get shown as latest version

[david-jointech]

Description

When creating a devrelease after having created a release-candidate for the same version, commitizen -p shows the release-candidate and not the devrelease. I'm using the scm-version_provider.

Generally the error seems in a way expected to me, since the scm-provider has no way of knowing the devrelease tag is actually newer than the release-candidate. I think the behavior could be mitigated, if generating a devrelease would append to the release-candidate (so creating e.g. 0.12.0-rc0-dev1083) instead of appending to the normal version number (0.12.0-dev1083).

Steps to reproduce

1. Create a release-candidate cz bump --yes --changelog --prerelease rc. In our case the version 0.12.0-rc0 is generated
2. Create a devrelase cz bump --yes --changelog --devrelease 1083. Now we have the version 0.12.0-dev1083
3. Check the version with cz version -p

Current behavior

cz version -p returns 0.12.0-rc0

Desired behavior

cz version -p should return 0.12.0-dev1083.

Alternatively, cz bump --yes --changelog --devrelease 1083 should create 0.12.0-rc0-dev1083 and then cz version -p should return that.

Screenshots

No response

Environment

Commitizen Version: 3.27.0
Python Version: 3.12.3 (main, Apr 23 2024, 09:16:07) [GCC 13.2.1 20240417]
Operating System: Linux