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_incremental is set as default when calling changelog from cz bump #883
cz bump with changelog_incremental = false on pyproject.toml doesn't have any effect when calling cz bump --changelog or cz bump with update_changelog_on_bump = true`.
Steps to reproduce
Define changelog_incremental = false and update_changelog_on_bump = true
changed the title [-]Good bug title tells us about precise symptom, not about the root cause.[/-][+]changelog_incremental is set as default when calling changelog from cz bump[/+]on Oct 11, 2023
We'd appreciate it if you're interested in sending us a PR. 🙂 I think this should be an easy and small one. Other than the value change, all we need is adding a few tests
Triage from #1964: Confirmed still valid on master (4.15.1). commitizen/commands/bump.py (line 317) hardcodes "incremental": True in the changelog args passed when bumping, which overrides changelog_incremental = false from config. Fix: read self.config.settings.get("changelog_incremental", True). There's already an issue-status: pr-created PR — needs a review.
Setup: cz_conventional_commits with changelog_incremental = false and update_changelog_on_bump = true. Bumped once (v0.2.0), then manually inserted # This should be regenerated at the top of CHANGELOG.md, then committed feat: C and bumped again.
Expected (with incremental = false): the corrupted line should be gone — full regeneration.
Actual after second bump:
# This should be regenerated## v0.3.0 (2026-05-09)
...
The corrupted line persists, confirming cz bump used incremental mode despite the config.
Verdict: STILL VALID. As I noted in the triage, commitizen/commands/bump.py:317 hardcodes "incremental": True. Should read self.config.settings.get("changelog_incremental", True). There's already an open PR labeled issue-status: pr-created — needs review.
Activity
[-]Good bug title tells us about precise symptom, not about the root cause.[/-][+]changelog_incremental is set as default when calling changelog from cz bump[/+]Lee-W commentedon Oct 17, 2023
Hi @LuisHenri , thanks for reporting this issue. I've verified this is indeed a valid bug.
Lee-W commentedon Oct 17, 2023
We'd appreciate it if you're interested in sending us a PR. 🙂 I think this should be an easy and small one. Other than the value change, all we need is adding a few tests
fix(commands/bump): prevent using incremental changelog when it is se…
bearomorphism commentedon May 9, 2026
Triage from #1964: Confirmed still valid on master (4.15.1).
commitizen/commands/bump.py(line 317) hardcodes"incremental": Truein the changelog args passed when bumping, which overrideschangelog_incremental = falsefrom config. Fix: readself.config.settings.get("changelog_incremental", True). There's already anissue-status: pr-createdPR — needs a review.bearomorphism commentedon May 9, 2026
Verification update (re #1964)
Reproduced against current master (4.15.1):
Setup:
cz_conventional_commitswithchangelog_incremental = falseandupdate_changelog_on_bump = true. Bumped once (v0.2.0), then manually inserted# This should be regeneratedat the top of CHANGELOG.md, then committedfeat: Cand bumped again.Expected (with
incremental = false): the corrupted line should be gone — full regeneration.Actual after second bump:
The corrupted line persists, confirming
cz bumpused incremental mode despite the config.Verdict: STILL VALID. As I noted in the triage,
commitizen/commands/bump.py:317hardcodes"incremental": True. Should readself.config.settings.get("changelog_incremental", True). There's already an open PR labeledissue-status: pr-created— needs review.