merge queue: embarking main (8980236), #344 and [#349 + #342] together

[mergify]

✨ The pull request #342 has been manually updated. The pull request #349 has been re-embarked. ✨

Branch main (8980236), #344 and [#349 + #342] are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of [#349 + #342].
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule pre-commit Updates for merge:

• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections
• author = renovate[bot]
  • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.11.17 #342
  • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.15.15 #349
• files ~= .pre-commit-config.yaml

---
checking_base_sha: b32c8b91eb6846fdafb72b5490fcfa1ba6508b28
previous_failed_batches: []
pull_requests:
  - number: 349
    scopes: []
  - number: 342
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates pre-commit hook versions and minimum supported Python version, and refreshes the uv lockfile accordingly as part of a Renovate-driven pre-commit update batch in the merge queue.

Sequence diagram for updated pre-commit hook execution

sequenceDiagram
  actor Developer
  participant Git as Git
  participant PreCommit as pre_commit
  participant UvHook as uv_pre_commit
  participant RuffHook as ruff_pre_commit

  Developer->>Git: git commit
  Git->>PreCommit: trigger hooks
  PreCommit->>UvHook: run uv-sync (rev 0.11.6)
  UvHook-->>PreCommit: dependencies synchronized
  PreCommit->>UvHook: run uv-lock --offline (rev 0.11.6)
  UvHook-->>PreCommit: lockfile updated
  PreCommit->>RuffHook: run ruff-check --fix (rev v0.15.10)
  RuffHook-->>PreCommit: lint and auto-fix issues
  PreCommit-->>Git: all hooks passed
  Git-->>Developer: commit succeeds

Loading

Flow diagram for Python version bump and lockfile refresh

flowchart TD
  A["Update pyproject.toml
  requires-python >=3.14.4,<3.15"] --> B["Run uv-sync
  via uv-pre-commit 0.11.6"]
  B --> C["Run uv-lock --offline
  regenerate uv.lock"]
  C --> D["Commit changes
  .pre-commit-config.yaml,
  pyproject.toml, uv.lock"]
  D --> E["CI runs with
  new Python constraint
  and updated dependencies"]

Loading

File-Level Changes

Change	Details	Files
Bump versions of uv and ruff pre-commit hooks to newer releases.	Update uv-pre-commit hook revision from 0.11.3 to 0.11.6 for uv-sync and uv-lock hooks Update ruff-pre-commit hook revision from v0.15.9 to v0.15.10 for ruff-check hook	.pre-commit-config.yaml
Adjust project Python version constraint and refresh dependency lockfile.	Increase minimum required Python version from 3.14.3 to 3.14.4 while keeping upper bound at <3.15 Regenerate uv.lock to align with the updated Python constraint and tool versions	pyproject.toml uv.lock

---

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.

[deepsource-io]

DeepSource Code Review

We reviewed changes in 8980236...c587ae4 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Python		Apr 9, 2026 9:05p.m.	Review ↗
Secrets		Apr 9, 2026 9:05p.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[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