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
changelog is not able to recognize tags for incremental changelog #1149
> cz bump --dry-run
bump: version 0.1.3 → 0.2.0
tag to create: utility/v0.2.0
increment detected: MINOR
InvalidVersion GitTag('utility/v0.1.3', 'a6ffd4da2c7db27a792b00fefdbca5e7de6f1f60', '2024-05-17')
InvalidVersion GitTag('utility/v0.1.2', 'cb887f77eaca3ae2af4360a9451d18ec5414bdb6', '2024-05-16')
No tag found to do an incremental changelog
It looks like, it recognize current release version but it is not able to match the correct tag to generate incremental changelog
Triage from #1964: Looks fixed on master (4.15.1) — same fix as #845. commitizen/tags.py's TagRules correctly matches custom tag_format = "utility/v$version". Could anyone confirm a fresh repro? If so, closing recommended.
Activity
Lee-W commentedon Aug 11, 2024
Thanks for reporting this issue. I just verified this.
Lee-W commentedon Aug 11, 2024
I dug into it a bit. This happens in
commitizen/commitizen/changelog.py
Line 96 in 01fd042
versionintoschemeinstead oftagbearomorphism commentedon May 9, 2026
Triage from #1964: Looks fixed on master (4.15.1) — same fix as #845.
commitizen/tags.py'sTagRulescorrectly matches customtag_format = "utility/v$version". Could anyone confirm a fresh repro? If so, closing recommended.bearomorphism commentedon May 9, 2026
Verification update (re #1964)
I reproduced this against current master (4.15.1):
pyproject.tomlwith the exact config from this issue (tag_format = "utility/v$version",version_scheme = "semver2",version_provider = "poetry",changelog_incremental = true,major_version_zero = true).After two bumps,
git tag --list:cz changelogexits 0 with noInvalidVersionwarnings, and theCHANGELOG.mdcorrectly groups all releases:Verdict: FIXED —
TagRules(incommitizen/tags.py) now correctly handles customtag_formatprefixes. Closing-eligible.bearomorphism commentedon May 9, 2026
Feel free to reopen is this issue still persists, thanks!