Skip to content

chore: update commitizen version to use v<version number> and add#37

Merged
goapunk merged 1 commit into
mainfrom
fix-commitizen-version
Apr 14, 2026
Merged

chore: update commitizen version to use v<version number> and add#37
goapunk merged 1 commit into
mainfrom
fix-commitizen-version

Conversation

@goapunk

@goapunk goapunk commented Mar 25, 2026

Copy link
Copy Markdown
Owner

release flow to readme

@goapunk goapunk requested a review from decentral1se March 25, 2026 22:58

@decentral1se decentral1se left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Comment thread README.md
3. install commitizen: `pip install commitizen`
4. run `cz bump`
5. push to a new branch and make pr
6. once merged, delete the tag created by commitizen, tag the release commit on main and push it

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of weird that you have to delete the tag and tag again but I'm fine with it ☺️

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it's a bit of a hack, otherwise we would have to push directly to main. I guess something like

cz bump --files-only --yes --changelog
git commit -am "bump: release $(cz version --project)"

would make more sense. Or just having a GitHub action do the whole process. Maybe I'll add that instead.

@goapunk goapunk merged commit 11b8de6 into main Apr 14, 2026
1 check passed
@goapunk goapunk deleted the fix-commitizen-version branch April 14, 2026 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants