[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/pre-commit/pre-commit-hooks: v4.6.0 → v6.0.0
• github.com/asottile/pyupgrade: v3.17.0 → v3.21.2
• https://github.com/psf/black → https://github.com/psf/black-pre-commit-mirror
• github.com/psf/black-pre-commit-mirror: 24.8.0 → 26.5.1
• github.com/PyCQA/isort: 5.13.2 → 9.0.1
• github.com/asottile/setup-cfg-fmt: v2.5.0 → v3.2.0
• github.com/kynan/nbstripout: 0.7.1 → 0.9.1
• github.com/nbQA-dev/nbQA: 1.8.7 → 1.9.1
• github.com/PyCQA/flake8: 7.1.1 → 7.3.0
• github.com/PyCQA/flake8: 7.1.1 → 7.3.0
• github.com/pre-commit/mirrors-mypy: v1.11.2 → v2.3.1
• github.com/rstcheck/rstcheck: v6.2.4 → v6.3.0
• github.com/codespell-project/codespell: v2.3.0 → v2.4.3

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, pre-commit-ci[bot]!). We assume it knows what it's doing!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[greptile-apps]

Greptile Summary

This PR updates the pre-commit toolchain and applies the resulting formatting changes. The main changes are:

• Updated pre-commit hook revisions.
• Switched Black to the pre-commit mirror repository.
• Applied formatter cleanup across Python source and test files.
• Updated generated setup metadata.

Confidence Score: 4/5

This should be fixed before merging.

• The Python import formatter is still pinned to a beta release.
• Local and CI formatting can change or fail based on prerelease formatter behavior.

Files Needing Attention: .pre-commit-config.yaml

Important Files Changed

Filename	Overview
.pre-commit-config.yaml	Pre-commit hook versions were updated, but the isort hook still uses a beta release.

_{Reviews (13): Last reviewed commit: "[pre-commit.ci] auto fixes from pre-comm..." | Re-trigger Greptile}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[greptile-apps]

Beta isort pin

This still runs the isort hook from a 9.0 beta tag. The hook is reached on every local and CI pre-commit run, so import formatting now depends on pre-release formatter behavior. Pinning this hook to a stable isort release avoids CI churn from beta sorting changes.

Suggested change

	- repo: https://github.com/PyCQA/isort
	rev: 5.13.2
	rev: 9.0.0b1
	- repo: https://github.com/PyCQA/isort
	rev: 8.0.1

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!

[greptile-apps]

Avoid beta formatter This hook still points at an isort beta release. The formatter runs on Python files during local and pre-commit.ci checks, so import formatting can depend on non-final isort behavior and can change or fail before a stable release. Pinning this hook to a stable isort release avoids CI churn from prerelease formatter changes.

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!

[greptile-apps]

Avoid beta formatter

This still pins the Python import sorter to a beta release. The hook runs on Python files during local pre-commit and pre-commit.ci checks, so formatting can depend on non-final isort behavior and can change or fail before the release line stabilizes. Pin this hook to a stable isort release instead.

Suggested change

	rev: 9.0.0b1
	rev: 8.0.1

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!

[greptile-apps]

Avoid beta formatter

This hook still pins isort to a beta release. The hook runs during local and pre-commit.ci checks for Python files, so import formatting can depend on prerelease behavior and can change or fail before the release line is stable. Pin this hook to a stable isort release instead.

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!

[sonarqubecloud]

Quality Gate passed

Issues
23 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud