merge queue: embarking main (a4ccdc8), #348, #349 and #337 together

[mergify]

✨ Pull request #349 which was ahead in the queue has been dequeued (for the following reason: pull request manually updated). The pull request #337 has been re-embarked. ✨

Branch main (a4ccdc8), #348, #349 and #337 are embarked together for merge.

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

Required conditions of queue rule Python Dependency Updates for merge:

• check-success = Test Image / API Test
• 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:

• author = renovate[bot]
  • chore(deps): lock file maintenance #337
• check-success = Check Dependency Compatibility
• files ~= ^(uv.lock|pyproject.toml)$
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

---
checking_base_sha: 91f6f9fec58e39423435f8efb38ecdeebcb1d7bb
previous_failed_batches: []
pull_requests:
  - number: 337
    scopes: []
scopes: []
...

[deepsource-io]

DeepSource Code Review

We reviewed changes in a4ccdc8...b9b06d0 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:17p.m.	Review ↗
Secrets		Apr 9, 2026 9:17p.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.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Ruff linter version used by development tooling and pre-commit, and refreshes the Python dependency lockfile accordingly as part of an automated merge-queue PR.

Flow diagram for updated Ruff linter usage in development tooling

flowchart TD
  Developer[Developer] --> GitCommit[Create commit]
  GitCommit --> PreCommit[Run pre-commit]
  PreCommit --> RuffPreCommitHook[Ruff pre-commit hook]
  RuffPreCommitHook --> RuffCli01510[Ruff CLI v0.15.10]
  RuffCli01510 --> Codebase[Apply lint fixes and checks]

  subgraph ToolingConfig[Tooling configuration]
    PreCommitConfig[".pre-commit-config.yaml<br/>rev = v0.15.10"] --> RuffPreCommitHook
    PyprojectToml["pyproject.toml<br/>dev ruff>=0.15.10"] --> RuffCli01510
    UvLock["uv.lock<br/>resolved Ruff deps"] --> RuffCli01510
  end

Loading

File-Level Changes

Change	Details	Files
Bump Ruff version in pre-commit configuration to align with updated tooling.	Update the astral-sh/ruff-pre-commit hook revision from v0.15.9 to v0.15.10 Keep existing hook configuration (ruff-check with --fix) unchanged aside from the version reference	.pre-commit-config.yaml
Update the development dependency constraint for Ruff and regenerate the lockfile.	Increase the Ruff dev dependency lower bound from >=0.15.9 to >=0.15.10 in the dev dependency group Regenerate uv.lock to capture the new Ruff version and any resulting dependency resolution changes	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.

[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