Skip to content

Update commitizen to 4.13.7 #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pyup-bot wants to merge 1 commit into from
Closed

Update commitizen to 4.13.7 #157

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ playwright==1.55.0

# dev
black==25.9.0
commitizen==4.9.1
commitizen==4.13.7
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Feb 9, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

commitizen 4.13.7 release notes changelog

💡 Result:

Commitizen v4.13.7 (2026-02-09) — Release notes / changelog

Fix

  • provider: use encoding settings in config (#1857) [1]

Release/tag: v4.13.7 (commit dd972c9) [1]

Sources

  • [1] Commitizen GitHub Releases page (v4.13.7 entry): (github.com)

Citations:

🌐 Web query:

commitizen 4.13.7 Python version support requirements

💡 Result:

Commitizen 4.13.7 declares Requires-Python: >=3.10, <4.0 (i.e., Python 3.10+; not Python 4). [1]

Sources:
[1] PyPI – commitizen 4.13.7 project metadata (“Requires: Python <4.0, >=3.10”) (pypi.org)

Citations:

🌐 Web query:

commitizen breaking changes 4.10 to 4.13 CLI behavior

💡 Result:

Breaking / potentially breaking changes (4.10.x → 4.13.x)

  • Python runtime support: Commitizen 4.11.0 drops Python 3.9 support (install/runtime break if you were on 3.9). [2]
  • Hook tooling change: 4.12.0 switches its hook integration from pre-commit to prek (if you rely on Commitizen’s provided git hooks / pre-commit setup, expect config + installation workflow differences). [3]
  • CLI flag deprecation (behavior change for scripts): 4.13.0 adds cz bump --version-files-only and deprecates --files-only (old flag still works for now, but scripts should be updated). [4]

Other notable CLI behavior changes in this range

  • cz version: 4.13.0 adds a --tag option. [4]
  • CLI UX / output: 4.13.0 adds descriptions when choosing a commit rule and tweaks help-text capitalization/grammar; also aligns message_length_limit behavior. [4]
  • CLI crash/exception handling fix: 4.11.4 fixes a CLI exception-hook override/argv-related issues. [5]
  • (Baseline at 4.10.0) 4.10.0 includes CLI-adjacent behavior like allowing amend! prefix and “exclamation in title” parsing for breaking changes (not a breaking change itself, but can affect parsing). [1]

Sources: GitHub release notes for v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.11.4. [1][2][3][4][5]

Verify Python 3.9 support and pre-commit hook compatibility before upgrading.

Commitizen 4.13.7 requires Python ≥3.10 (drops Python 3.9 support). Additionally, this range includes a significant tooling change: v4.12.0 switched hook integration from pre-commit to prek, which affects CI/pre-commit workflows. Confirm the project supports Python 3.10+ and update any pre-commit or CI configurations accordingly. Also note v4.13.0 deprecated --files-only in favor of --version-files-only; verify no release scripts rely on the old flag.

🤖 Prompt for AI Agents 
In `@requirements.txt` at line 7, The requirements pin to commitizen==4.13.7 which
drops Python 3.9 and changes hook integration; verify CI/build and local
environments support Python >=3.10, update project Python compatibility metadata
(pyproject/CI jobs) and any tox/Docker configs if necessary, and inspect
CI/pre-commit configs for use of "pre-commit" hooks—if present switch to "prek"
or adjust to the new integration used by Commitizen >=4.12.0; also search
release scripts for the deprecated flag "--files-only" and replace it with
"--version-files-only" (or adjust the script logic) to ensure compatibility with
commitizen (symbols to check: commitizen, prek, pre-commit, --files-only,
--version-files-only).

invoke==2.2.0
isort==6.1.0
mypy==1.18.2
Expand Down