[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/pre-commit/pre-commit-hooks: v4.5.0 → v6.0.0
• https://github.com/psf/black → https://github.com/psf/black-pre-commit-mirror
• github.com/psf/black-pre-commit-mirror: 24.1.1 → 26.3.1
• github.com/tox-dev/tox-ini-fmt: 1.3.1 → 1.7.1
• github.com/asottile/pyupgrade: v3.15.0 → v3.21.2
• github.com/hadialqattan/pycln: v2.4.0 → v2.6.0
• github.com/pycqa/isort: 5.13.2 → 9.0.0a3
• github.com/pycqa/flake8: 7.0.0 → 7.3.0
• github.com/pre-commit/mirrors-mypy: v1.8.0 → v1.20.2
• github.com/yoheimuta/protolint: v0.47.5 → v0.56.4
• github.com/gitleaks/gitleaks: v8.18.2 → v8.30.0
• github.com/igorshubovych/markdownlint-cli: v0.39.0 → v0.48.0
• github.com/pycqa/docformatter: v1.7.7 → v1.7.8
• github.com/adrienverge/yamllint: v1.34.0 → v1.38.0
• github.com/rhysd/actionlint: v1.6.26 → v1.7.12
• github.com/hadolint/hadolint: v2.12.0 → v2.14.0

[greptile-apps]

Greptile Summary

This is a pre-commit.ci autoupdate bumping 16 tool revisions in .pre-commit-config.yaml, along with a required stage rename (commit → pre-commit) for pre-commit v3+ compatibility.

• isort is pinned to 9.0.0a3, an alpha pre-release; alpha builds can change behavior before going stable and should generally be avoided in shared developer tooling.

Confidence Score: 4/5

Safe to merge with low risk; the alpha isort pin is the only notable concern and isort is already in ci.skip so CI is unaffected.

One P1 finding (alpha pre-release for isort) with limited blast radius since isort is skipped in CI and only affects local developer runs. All other bumps are stable releases with no red flags.

.pre-commit-config.yaml — specifically the isort 9.0.0a3 alpha pin at line 101.

Important Files Changed

Filename	Overview
.pre-commit-config.yaml	Routine version bumps across 16 tools; notable concerns are isort pinned to an alpha pre-release (9.0.0a3), a major jump in pre-commit-hooks (v4→v6), and the required default_stages rename from commit to pre-commit for pre-commit v3+ compatibility.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    trigger["git commit / pre-commit run"] --> stage["default_stages: pre-commit\n(renamed from 'commit')"]
    stage --> linters["Linters & Formatters"]
    stage --> typecheck["Type Checking"]
    stage --> security["Security"]
    stage --> other["Other Tools"]
    linters --> black["black 26.3.1\n⚠ skipped in CI"]
    linters --> isort["isort 9.0.0a3 ⚠️ alpha\n⚠ skipped in CI"]
    linters --> flake8["flake8 7.3.0\n⚠ skipped in CI"]
    typecheck --> mypy["mypy v1.20.2\n⚠ skipped in CI"]
    security --> gitleaks["gitleaks v8.30.0 ✅"]
    security --> detectpk["detect-private-key ✅"]
    other --> precommithooks["pre-commit-hooks v6.0.0 ✅"]
    other --> yamllint["yamllint v1.38.0 ✅"]
    other --> actionlint["actionlint v1.7.12 ✅"]

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
.pre-commit-config.yaml:101
**Alpha pre-release pinned for isort**

`isort` has been pinned to `9.0.0a3`, which is the third alpha of the 9.0.0 release cycle. Alpha releases are explicitly unstable: APIs, default behaviors, and configuration parsing can change without notice between alpha iterations and the final stable release. If `9.0.0` introduces further breaking changes before going stable, the pinned alpha would need to be updated again. Consider waiting for the stable `9.0.0` release to avoid chasing a moving target in the toolchain.

_{Reviews (2): Last reviewed commit: "[pre-commit.ci] pre-commit autoupdate" | Re-trigger Greptile}

[greptile-apps]

Alpha pre-release pinned for isort

isort has been pinned to 9.0.0a3, which is the third alpha of the 9.0.0 release cycle. Alpha releases are explicitly unstable: APIs, default behaviors, and configuration parsing can change without notice between alpha iterations and the final stable release. If 9.0.0 introduces further breaking changes before going stable, the pinned alpha would need to be updated again. Consider waiting for the stable 9.0.0 release to avoid chasing a moving target in the toolchain.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .pre-commit-config.yaml
Line: 101

Comment:
**Alpha pre-release pinned for isort**

`isort` has been pinned to `9.0.0a3`, which is the third alpha of the 9.0.0 release cycle. Alpha releases are explicitly unstable: APIs, default behaviors, and configuration parsing can change without notice between alpha iterations and the final stable release. If `9.0.0` introduces further breaking changes before going stable, the pinned alpha would need to be updated again. Consider waiting for the stable `9.0.0` release to avoid chasing a moving target in the toolchain.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!