Wrong precedence of tags on same commit

[krumlo]

Description

If I have a tag 1.2.3-rc1 on a commit, and all internal QA testing has passed, I want to be able to say that the same commit is now 1.2.3, without a specific bump commit. (I'd prefer to just push a tag to start release process, rather then merge a bump to main and sync with prod).

Steps to reproduce

1. Put two tags (1.2.3-rc1 and 1.2.3) on the same commit
2. Generate a changelog with --merge-prerelease

Current behavior

Commits gets grouped under 1.2.3-rc1.

Desired behavior

I would expect precedence of tags on same commit to be 1.2.3-rc1 < 1.2.3.

SemVer 1.0 specification does not seem to say anything about precedence for .dev versions, but I would expect them to be 1.2.3-rc1.dev1 < 1.2.3-rc1.dev2 < 1.2.3-rc1 < 1.2.3, but I'm not sure about that one.

Screenshots

No response

Environment

commitizen version 3.22.0
python version 3.8.10
os Ubuntu 20.04 on WSL

[krumlo]

Seems like the problem is due to how git sorts normal tags, since they contain no date/time of the actual tag, just the commit it is attached to. If I use annotated tags it works as expected.