You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
scm provider cant find current tag with build metadata if matched by legacy_tag_formats #2015
When using version_provider = "scm" and a legacy tag format that matches PEP 440 prerelease tags with local/build metadata, commitizen appears to match the tag but fails to use it as the current tag for bump.
Even if a reachable tag like 1.0.1rc0+gha exists and should be used, cz bump --prerelease rc --build-metadata gha reports that no matching tag could be found.
No tag matching configuration could be found.
Possible causes:
- version in configuration is not the current version
- tag_format or legacy_tag_formats is missing, check them using 'git tag --list'
? Is this the first tag created? No
1.1.0rc0+gha
Current behavior
Even if a tag like 1.0.1rc0+gha` exists, Commitizen reports:
No tag matching configuration could be found.
Possible causes:
- version in configuration is not the current version
- tag_format or legacy_tag_formats is missing, check them using 'git tag --list'
If answering No to “Is this the first tag created?”, Commitizen appears to compute from more history than expected instead of using 1.0.1rc0+gha:
? Is this the first tag created? No
1.1.0rc0+gha
Desired behavior
If the current tag is of the pattern 1.0.1rc0+gha, cz should recognize it and properly bump to 1.0.1rc1+gha when using cz bump --prerelease rc --build-metadata gha --get-next
Screenshots
No response
Environment
Commitizen Version: 4.16.3
Python Version: 3.14.6 (main, Jun 11 2026, 04:03:53) [Clang 22.1.3 ]
Operating System: Linux
Activity