[pre-commit-ci]

updates:

• github.com/PyCQA/isort: 9.0.1 → 9.0.2
• github.com/psf/black-pre-commit-mirror: 26.5.1 → 26.10.0
• github.com/commitizen-tools/commitizen: v4.18.1 → v4.19.1
• github.com/pre-commit/mirrors-mypy: v2.3.1 → v2.4.0

[llamapreview]

LlamaPReview — No blocking issues found

Reviewed changed regions in .pre-commit-config.yaml.

Review details and evidence

Material unknowns

• The upstream content of commitizen v4.19.0 — specifically whether that release renamed or removed the commitizen hook id or changed the hook's entry contract — is not in evidence; the supplied evidence covers this repository only. If upstream changed the hook id or entry contract, the commit-msg stage would fail on the next matching commit, a failure this PR would then have introduced. Deep classified this as nondeciding: the hook id is unchanged in this repo's config, pre-commit.ci - pr succeeds at this head, the change is a routine automated autoupdate, and any such breakage is trivially revertible with no product or data consequence. An answer would change severity only, not the merge posture.
  • Check: No pre-merge action required. Optionally consult commitizen v4.19.0 release notes if the maintainer wants upstream-content confirmation.

LlamaPReview checks

• Reviewed changed regions in .pre-commit-config.yaml.
• Read the complete PR-head file .pre-commit-config.yaml.

---

LlamaPReview is an open-source pull request reviewer. See exactly what it will and will not publish.