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
Tag name validation issue on cz bump --changelog #845
When generating changelog, get_version_tags function from commitizen/changelog.py is validating existing tags as if they were version names with no additional text on them. This behavior conflicts with the feature of customizing tag_format
Steps to reproduce
Use some custom prefixed tag_format in .cz.yaml, tag_format: some-project-release-$version
Do initial version commit, bump and generate changelog: cz bump --changelog
Do subsequent fix/feat commit, bump and generate changelog: cz bump --changelog
ER: Version bumped, changelog generated.
AR: Error saying No tag found to do an incremental changelog
Current behavior
get_version_tags function from commitizen/changelog.py is validating tag names as if they where version names, hence it's not able to return existing custom tags, an error appears saying No tag found to do an incremental changelog
Desired behavior
Allow the changelog to generate regardless of tag name custom prefixes, possible solution could be to exclude the tag name prefix when checking with scheme(tag.name)
Triage from #1964: Looks fixed on master (4.15.1). commitizen/tags.py now contains a TagRules class that handles custom tag_format (including arbitrary prefixes like some-project-release-$version) via regex-based is_version_tag / extract_version. Could anyone confirm a fresh repro is now passing? If so, this can be closed (and #1149 along with it).
Activity
saivenky commentedon Sep 14, 2023
I'm having the same issue. This would be fixed by #692 (which is linked to issue #519).
hermanho commentedon May 8, 2024
When can fix it? I cannot use commitizen in a monorepo repo and the config tag_format is useless.
AlexeySanko commentedon May 24, 2024
Looks as great feature for monorepo. Any update on it?
bearomorphism commentedon May 9, 2026
Triage from #1964: Looks fixed on master (4.15.1).
commitizen/tags.pynow contains aTagRulesclass that handles customtag_format(including arbitrary prefixes likesome-project-release-$version) via regex-basedis_version_tag/extract_version. Could anyone confirm a fresh repro is now passing? If so, this can be closed (and #1149 along with it).bearomorphism commentedon May 9, 2026
Verification update (re #1964)
I reproduced this against current master (4.15.1):
Config (
.cz.yaml):cz_conventional_commitswithtag_format: "some-project-release-$version"andupdate_changelog_on_bump: true.After two bumps:
git tag --list:CHANGELOG.md:Both bumps succeeded; no
No tag found to do an incremental changelogerror.Verdict: FIXED — closing-eligible.
TagRulesincommitizen/tags.pynow properly handles custom prefixedtag_formatvia regex matching.bearomorphism commentedon May 9, 2026
Feel free to reopen is this issue still persists, thanks!