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

[mergify]

✨ The pull request #349 has been manually updated. ✨

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

This pull request has been created by Mergify to speculatively check the mergeability of #349.
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:

• author = renovate[bot]
  • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.15.12 #349
• files ~= .pre-commit-config.yaml
• 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: 11b512c4ca5ce7a1a16e87f702dc82183df83a5b
previous_failed_batches: []
pull_requests:
  - number: 349
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Ruff linter version across tooling configuration and lockfile as part of a Renovate-driven pre-commit maintenance PR, validated via a Mergify merge queue batch with main and #348/#349.

Flow diagram for Ruff version update across configuration files

flowchart TD
  A[Start: Renovate detects new Ruff version v0.15.10] --> B[Update .pre-commit-config.yaml
rev v0.15.9 -> v0.15.10]
  B --> C[Update pyproject.toml
dev dependency ruff>=0.15.9 -> ruff>=0.15.10]
  C --> D[Regenerate uv.lock
with new Ruff version]
  D --> E[Open PR 349 with version bumps]
  E --> F[Mergify merge queue
embarks main, 348, 349]
  F --> G[Run Mergify Merge Protections checks]
  G --> H{All required checks pass?}
  H -->|Yes| I[Merge batch into main]
  H -->|No| J[Keep in queue or fail PR]
  I --> K[End]
  J --> K[End]

Loading

File-Level Changes

Change	Details	Files
Bump Ruff linter version in pre-commit and development dependencies, updating the lockfile accordingly.	Update astral-sh/ruff-pre-commit hook revision from v0.15.9 to v0.15.10 in the pre-commit configuration. Increase the minimum Ruff version in the dev dependency group from 0.15.9 to 0.15.10 in the project configuration. Regenerate or adjust uv.lock to reflect the new Ruff version and ensure dependency consistency.	.pre-commit-config.yaml pyproject.toml uv.lock

Possibly linked issues

• #0: The PR’s ruff and ruff-pre-commit version bumps correspond directly to updates listed in the Renovate dependency dashboard.

---

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 a4ccdc8...16a7caa 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:16p.m.	Review ↗
Secrets		Apr 9, 2026 9:16p.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