fix: use semver2 version scheme and fetch tags for pre-release compat…#71
Merged
nikosxenakis merged 1 commit intomainfrom Mar 23, 2026
Merged
Conversation
lwshang
approved these changes
Mar 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--version-scheme semver2instead ofsemverin all commitizen actions (bump-version,generate-release-notes,generate-changelog)fetch-tags: trueto the checkout step in thegenerate-changelogreusable workflowThe
semverscheme uses Python's PEP 440 normalization, which convertsbeta.0→b0(commitizen-tools/commitizen#1025, commitizen-tools/commitizen#150). This causes tag mismatches — commitizen looks forv5.2.0-b0but the actual tag isv5.2.0-beta.0— resulting inCould not find a valid revision rangeerrors during changelog and release notes generation.The
semver2scheme follows the strict semver spec and preserves pre-release identifiers as-is. No behavior change for stable releases.