Introduce --next flag on cz version --project #1678

Activity

1. woile

   added a parent issue on Nov 30, 2025

   • Add new capabilities to cz version #1677
2. woile

   added

   type: featureA new enhacement proposalA new enhacement proposal

   on Nov 30, 2025
3. github-actions

   added

   issue-status: needs-triage

   on Nov 30, 2025
4. Lee-W

   added

   issue-status: wait-for-implementationmaintainers agree on the bug / featuremaintainers agree on the bug / feature

   and removed

   issue-status: needs-triage

   on Dec 3, 2025
5. Lee-W

   added the

   Feature

   issue type on Dec 3, 2025
6. bearomorphism

   self-assigned this

   on Dec 12, 2025
7. bearomorphism

   added 2 commits that reference this issue on May 3, 2026

   docs: add TODO comment for USE_GIT_COMMITS future work (commitizen-to…

   ...

   2ca5b7e

   feat(version): add MANUAL_VERSION, --next and --patch to version comm…

   ...

   b5e0840
8. bearomorphism commented on May 9, 2026

   

   bearomorphism

   on May 9, 2026

   Collaborator

   More actions

   Cross-checked against master (v4.15.1) by an claude-opus-4.7 validation pass while triaging #1976.

   Status: partially fixed.

   Form	Status
   cz version --project --next MAJOR|MINOR|PATCH	implemented (commitizen/cli.py:577-587, commitizen/commands/version.py:93-103); covered by tests/commands/test_version_command.py::test_next_version
   cz version --project --next (no value, derive increment from commit history)	not implemented — explicit TODO at commitizen/commands/version.py:85-91 returns "--next USE_GIT_COMMITS is not implemented yet.", locked in by tests/commands/test_version_command.py:289-292

   The default --next form (no value) is the headline behaviour the issue asks for, so this issue should stay open until the bump-increment derivation in commitizen/commands/bump.py is refactored so version.py can call it and replace the USE_GIT_COMMITS TODO.

   (Surfaced via the round-3 triage in #1976.)