[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.15.17 → v0.15.18
• github.com/PyCQA/isort: 8.0.1 → 9.0.0a3
• github.com/igorshubovych/markdownlint-cli: v0.48.0 → v0.49.0

[greptile-apps]

Greptile Summary

This is an automated pre-commit autoupdate bump for three linting tools. Two updates are routine minor/patch releases; however, one bump warrants attention.

• ruff is patched from v0.15.17 → v0.15.18 (safe patch release).
• markdownlint-cli is bumped from v0.48.0 → v0.49.0 (safe minor release).
• isort is bumped from stable 8.0.1 to 9.0.0a3, an alpha pre-release, which could introduce unstable or breaking behavior in the import-sorting hook for all developers and CI pipelines.

Confidence Score: 3/5

Two of the three version bumps are routine stable releases and safe to merge; the isort bump to an alpha pre-release introduces risk of unstable linting behavior across all developer and CI environments.

The ruff and markdownlint-cli bumps are standard patch/minor releases with no meaningful risk. The isort upgrade from 8.0.1 to 9.0.0a3 pins an alpha to the project shared lint config — alpha releases can change output, break hooks, or be superseded quickly, causing spurious CI failures for every contributor.

.pre-commit-config.yaml — specifically the isort version bump to 9.0.0a3.

Important Files Changed

Filename	Overview
.pre-commit-config.yaml	Three pre-commit hook versions bumped: ruff (patch), markdownlint-cli (minor), and isort (8.0.1 → 9.0.0a3 — alpha pre-release, which may be unstable in CI).

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

[greptile-apps]

Alpha pre-release pinned in CI lint toolchain

isort is being bumped from the stable 8.0.1 to 9.0.0a3, an alpha pre-release. Alpha releases can introduce breaking changes, regressions, or unstable behavior between alpha iterations. Pinning an alpha in .pre-commit-config.yaml means every developer running pre-commit hooks and every CI pipeline will pick up this potentially unstable version. If the next pre-commit autoupdate pulls 9.0.0a4 or 9.0.0b1, import-sort output could change again, causing spurious diff failures. Consider waiting for a stable 9.x release before upgrading, or at minimum pinning to a beta rather than alpha.

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!