Repository navigation
Not possible to use --get-next when changelog is enabled #1640
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 forcefully marks changelog=false
What do you think @Lee-W @noirbizarre ?
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
Activity
bearomorphism commentedon Nov 12, 2025
Agree, that makes sense.
The current bump command is a little bloated to me. It would be great if we can move some of the instructions to other commands.
woile commentedon Nov 12, 2025
If you'll agree, we can start shipping these features to
cz versionunder v4. Although, we should isolate some functionality onbumpso it could be reused onversionfirst. And forv5we could deprecate--get-nextbearomorphism commentedon Nov 18, 2025
You can assign this feature to me. This will probably be 4.11 or later.
woile commentedon Nov 18, 2025
Wanna create a new ticket?
I'll work on the
setup-czaction 👍🏻bearomorphism commentedon Nov 18, 2025
Sounds good
Lee-W commentedon Nov 19, 2025
Sounds like a sound plan. Do we want to deprecate the original
--get-nextand remove it in v5?woile commentedon Nov 19, 2025
It depends, I would say yes, but only if it really makes
bumpleaner. If it's just 2 lines it's not a problem.Also, it would be nice to review
bumpand see if there's anything else we can removebearomorphism commentedon Nov 19, 2025
Maybe we can rename the option
--files-onlyto--version-files-onlyLee-W commentedon Nov 19, 2025
sounds like a good idea
woile commentedon Nov 20, 2025
I've built the setup-cz action, can you take a look? 🙏🏻
commitizen-tools/setup-cz#1
woile commentedon Nov 21, 2025
The new action is ready:
https://github.com/commitizen-tools/setup-cz
Lee-W commentedon Nov 30, 2025
now the action is there and #1645 is merged. I think we can close this one
woile commentedon Nov 30, 2025
I think the issue persists and
cz version -p --nextdoesn't exist. Shall I create a new ticket forcz version -p --nextinstead?Because the idea is to deprecate
--get-nextLee-W commentedon Nov 30, 2025
yep, it would be better and more clear this way