[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/pre-commit/pre-commit-hooks: v5.0.0 → v6.0.0
• github.com/astral-sh/ruff-pre-commit: v0.11.11 → v0.14.10
• https://github.com/psf/black → https://github.com/psf/black-pre-commit-mirror
• github.com/psf/black-pre-commit-mirror: 25.1.0 → 25.12.0
• github.com/pycqa/isort: 6.0.1 → 7.0.0
• github.com/pre-commit/mirrors-mypy: v1.15.0 → v1.19.1
• github.com/sourcery-ai/sourcery: v1.37.0 → v1.40.1b57

Summary by Sourcery

Update pre-commit configuration to use the latest versions of Ruff and MyPy hooks

CI:

• Bump ruff-pre-commit hook from v0.11.11 to v0.11.12
• Bump pre-commit/mirrors-mypy hook from v1.15.0 to v1.16.0

[sourcery-ai]

Reviewer's Guide

This PR updates the pre-commit hook versions for Ruff and mypy by bumping their rev entries in .pre-commit-config.yaml to the latest minor releases.

File-Level Changes

Change	Details	Files
Bump Ruff (ruff-pre-commit) hook version	Updated rev from v0.11.11 to v0.11.12	.pre-commit-config.yaml
Bump Mypy (mirrors-mypy) hook version	Updated rev from v1.15.0 to v1.16.0	.pre-commit-config.yaml

---

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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

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.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 86d690d1	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (86d690d)	Report Missing	Report Missing	Report Missing
Head commit (454576e)	2686	2646	98.51%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#43)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩