[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 → 8.0.1
• github.com/pycqa/flake8: 7.0.0 → 7.3.0
• github.com/pre-commit/mirrors-mypy: v1.8.0 → v1.20.0
• 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/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 routine automated pre-commit hook version update generated by pre-commit.ci, bumping 15 tools to their latest releases and migrating the black hook to the official psf/black-pre-commit-mirror repository.

Key changes:

• Stage name update: default_stages changed from commit → pre-commit, aligning with the renamed stage identifier introduced in pre-commit v3.2.0+
• black mirror migration: Switched from psf/black to psf/black-pre-commit-mirror (the officially recommended source for pre-commit users) and bumped to v26.3.1
• isort 5.13.2 → 8.0.1: Skips two major release lines (6.x and 7.x); may change import sorting behavior locally (isort is already in ci.skip so CI is unaffected)
• gitleaks v8.18.2 → v8.30.0: Improved secret detection coverage
• mypy v1.8.0 → v1.20.0: Improved type-checking accuracy
• All remaining bumps are minor or patch releases with no breaking changes expected

Confidence Score: 5/5

Safe to merge — all changes are automated version bumps with no application logic affected

Pure tooling maintenance PR with no application code changes. The only non-trivial detail is the isort major version jump (5→8), but since isort is in ci.skip it carries no CI risk. The default_stages rename is a correct compatibility fix for modern pre-commit. All feedback is P2 style only.

No files require special attention; optionally run pre-commit run isort --all-files locally to validate no unexpected import churn

Important Files Changed

Filename	Overview
.pre-commit-config.yaml	Routine autoupdate bumping 15 pre-commit hook versions; migrates black to the official mirror and renames default_stages from commit to pre-commit for pre-commit v3.2+ compatibility

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Developer git commit] --> B{default_stages: pre-commit}
    B --> C[pre-commit-hooks v6.0.0]
    B --> D[black v26.3.1
black-pre-commit-mirror]
    B --> E[isort v8.0.1]
    B --> F[flake8 v7.3.0]
    B --> G[mypy v1.20.0]
    B --> H[gitleaks v8.30.0]
    B --> I[protolint-docker v0.56.4]
    B --> J[hadolint-docker v2.14.0]
    C & D & E & F & G & H & I & J --> K{All checks pass?}
    K -->|Yes| L[Commit succeeds]
    K -->|No| M[Commit blocked]

Loading

Prompt To Fix All With AI

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

Comment:
**isort major version jump (5 → 8)**

`isort` has been bumped from `5.13.2` to `8.0.1`, skipping the `6.x` and `7.x` release lines entirely. Major version bumps in isort have historically introduced changes to default import grouping, section ordering, and profile behavior. While `isort` is listed in `ci.skip` (so CI pipelines are unaffected), developers running pre-commit locally may see unexpected large-scale import reformatting on first run.

It is worth running `pre-commit run isort --all-files` locally before merging to confirm no significant import churn is introduced that would warrant a follow-up cleanup PR.

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

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

[greptile-apps]

isort major version jump (5 → 8)

isort has been bumped from 5.13.2 to 8.0.1, skipping the 6.x and 7.x release lines entirely. Major version bumps in isort have historically introduced changes to default import grouping, section ordering, and profile behavior. While isort is listed in ci.skip (so CI pipelines are unaffected), developers running pre-commit locally may see unexpected large-scale import reformatting on first run.

It is worth running pre-commit run isort --all-files locally before merging to confirm no significant import churn is introduced that would warrant a follow-up cleanup PR.

Prompt To Fix With AI

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

Comment:
**isort major version jump (5 → 8)**

`isort` has been bumped from `5.13.2` to `8.0.1`, skipping the `6.x` and `7.x` release lines entirely. Major version bumps in isort have historically introduced changes to default import grouping, section ordering, and profile behavior. While `isort` is listed in `ci.skip` (so CI pipelines are unaffected), developers running pre-commit locally may see unexpected large-scale import reformatting on first run.

It is worth running `pre-commit run isort --all-files` locally before merging to confirm no significant import churn is introduced that would warrant a follow-up cleanup PR.

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