-
-
Notifications
You must be signed in to change notification settings - Fork 302
Open
Labels
Description
Description
It's not possible to properly use --get-next when setting update_changelog_on_bump = true (is true).
Steps to reproduce
- Create a
.cz.tomlwith
version = "0.0.1"
version_scheme = "semver2"
update_changelog_on_bump = true- Create a commit and bump normally
cz bump --yes - Add a new commit:
touch foo.txt
git add foo.txt
git commit -m "fix: foobar"- Try to get next version
cz bump --get-next - Observe error
--changelog or --changelog-to-stdout is not allowed with --get-nextThis would be fine, if there was a way to say --changelog=false or --no-changelog. But there's not. So this requires the user to "temporarly" set the flag in the .cz.toml to false, which in a CI it's painful.
Current behavior
There's no way to get the next version if the user has enabled update_changelog_on_bump in their settings
Desired behavior
I see 2 options, to discuss:
- Do not block on this setting when it's enabled
- Add a new flag
--no-changelogthat marks changelog=false
Screenshots
No response
Environment
Commitizen Version: 3.31.0
Python Version: 3.12.11 (main, Jun 3 2025, 15:41:47) [GCC 14.3.0]
Operating System: Linux