[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.16.2 → v0.16.5
• github.com/pre-commit/mirrors-mypy: v2.3.0 → v2.3.1
• github.com/abravalheri/validate-pyproject: v0.25 → 0.26
• github.com/rohaquinlop/complexipy-pre-commit: v6.2.0 → v7.0.1

Summary by Sourcery

Refresh pre-commit hooks and reformat affected documentation examples and type definitions.

Enhancements:

• Update pre-commit tooling dependencies, including Ruff, mypy, validate-pyproject, and complexipy.
• Apply formatting updates to Python code examples and type definitions in the documentation.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.pre-commit-config.yaml	41% smaller
docs/codedocs/api-reference/hypothesis-strategies.md	Unsupported file format
docs/codedocs/api-reference/types-and-protocols.md	Unsupported file format
docs/codedocs/geo-interface.md	Unsupported file format
docs/codedocs/guides/hypothesis-testing.md	Unsupported file format

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates pinned versions of three pre-commit hooks (ruff, mypy, and complexipy) in .pre-commit-config.yaml to their latest patch / minor releases, with no other behavioral or configuration changes.

File-Level Changes

Change	Details	Files
Bump versions of ruff, mypy, and complexipy pre-commit hooks to newer releases.	Update ruff-pre-commit hook revision from v0.16.2 to v0.16.3 for linting and formatting hooks Update mirrors-mypy hook revision from v2.3.0 to v2.3.1 for static type checking Update complexipy-pre-commit hook revision from v6.2.0 to v7.0.1 for cognitive complexity checks	.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.

[what-the-diff]

PR Summary

• Updating pre-commit hook for ruff-pre-commit
  The version of ruff-pre-commit has been updated from v0.16.2 to v0.16.3. This upgrade facilitates improved performance in the automatic code-review processes before commits, increasing the efficiency and quality of the code produced.

• Updating pre-commit hook for mypy
  The version of mypy has been upgraded from v2.3.0 to v2.3.1. This update will boost code accuracy and allow the detection of more types of errors at an early stage during the development process, thereby enabling quicker and more effective code rectification.

• Updating pre-commit hook for complexipy-pre-commit
  We've upgraded the complexipy-pre-commit from v6.2.0 to v7.0.1. This significant update aims to further optimize the complexity analysis of our code before it is committed, leading to simpler, more maintainable code.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a1812c6) to head (78fdd59).

Additional details and impacted files

@@            Coverage Diff            @@
##           develop      #385   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           32        32           
  Lines         2674      2674           
  Branches        91        91           
=========================================
  Hits          2674      2674           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Failed to generate code suggestions for PR

[llamapreview]

LlamaPReview — Blocking issues found

Ruff v0.16.3 activation of CPY001 makes the required static-tests check fail with 28 missing-copyright errors; do not merge until the pytest test files or Ruff config are updated.

Exact-head CI remains unresolved (3 failed); no CI-dependent merge-safety claim is made.

• Ruff v0.16.3 fails static-tests with 28 new CPY001 missing-copyright errors.

Owner action: Update the pre-commit hook config and test files or Ruff ignores so CPY001 no longer fails, then re-run static-tests.

Risk path

This focused view shows the single PR delta that verifies the blocking failure: the Ruff revision bump to v0.16.3 activates the CPY001 rule, causing the static-test check to fail at the PR head.

sequenceDiagram
participant PRC as PR Changes
participant RUFF as Ruff v0.16.3
participant CI as CI static-tests
participant OUT as Outcome
PRC->>RUFF: Activate ruff-check with selection ALL
note over RUFF: PR change - rev v0.16.3 activates CPY001
RUFF->>CI: Report 28 CPY001 errors (tests/*)
critical Blocking failure
CI->>OUT: Exit code 1 - check red
end
OUT-->>PRC: Merge blocked - fix or revert

Loading

Review details and evidence

Priority	File	Finding	Evidence
P1	.pre-commit-config.yaml	Ruff v0.16.3 fails static-tests with 28 new CPY001 missing-copyright errors.	confirmed

Material unknowns

• Whether Ruff v0.16.2 already enforced CPY001 and thus whether this failure is newly introduced or pre-existing. If v0.16.2 already enforced it, the failure is pre-existing debt rather than a new defect, but the head is still unmergeable and the owner action is unchanged.
  • Check: Check an existing base-branch CI log for static-tests under v0.16.2 to see if CPY001 failures already occurred.
• Whether the complexipy hook's major bump (v6.2.0 to v7.0.1) changes default behavior, output format, or exit status. A major-version hook can alter defaults or output format; the failure currently observed is only from Ruff, and no complexipy failure has been seen, so this is a nonblocking compatibility unknown.
  • Check: Verify the complexipy hook runs cleanly with v7.0.1 on a test environment or review its release notes/changelog.
• Whether the mypy and complexipy hooks actually ran successfully in the failing run. Since Ruff failed with CPY001, later hooks may not have been reached, so the absence of their output is not evidence of a pass.
  • Check: Re-run the static-tests job after fixing the Ruff failures to confirm the mypy and complexipy bumps are regression-free.

LlamaPReview checks

• Reviewed changed regions in .pre-commit-config.yaml.
• Read bounded PR-head context from pyproject.toml.

---

LlamaPReview reviewed this pull request at its exact head commit. Inspect the source or share feedback.

[llamapreview]

P1 | Confidence: High

The only changed component that can produce the observed output is the Ruff hook, whose rev changed from v0.16.2 to v0.16.3. The changed region enables ruff-check at the new revision. The pyproject.toml config selects ALL, which makes any rule added or newly stabilized by v0.16.3 active without further configuration; the ignore list and per-file-ignores for tests/*.py do not contain CPY001. The exact-head static-tests (3.14) logs show CPY001 Missing copyright notice at top of file for each test file (tests/<file>:1:1), Found 28 errors., and Process completed with exit code 1. The two runs fail identically. This makes the required static-test gate red at PR head, so merging unchanged would break the default branch's required checks.

Evidence: changed region in .pre-commit-config.yaml; bounded PR-head context from pyproject.toml.

[sourcery-ai]

Sourcery assessment

Approved.

[codescene-access]

No application code in the PR — skipped Code Health checks.

See analysis details in CodeScene

Quality Gate Profile: Customizable Safeguards
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.