merge queue: embarking main (8980236) and #344 together

[mergify]

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

Branch main (8980236) and #344 are embarked together for merge.

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

• 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 python to >=3.14.6,<3.15 #344
• check-success = Check Dependency Compatibility
• files ~= ^(uv.lock|pyproject.toml)$

---
checking_base_sha: 89802369900663710d632116122edb17471938de
previous_failed_batches: []
pull_requests:
  - number: 344
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the project’s minimum required Python patch version and refreshes the dependency lockfile as part of an automated Renovate/Mergify merge queue run.

Flow diagram for updated Python version requirement and lockfile refresh

flowchart LR
  Developer[Developer or CI] --> Update_request[Automated dependency update request]
  Update_request --> Pyproject_toml[pyproject.toml]
  Pyproject_toml -->|change requires-python from >=3.14.3,<3.15 to >=3.14.4,<3.15| Python_constraint[Updated Python version constraint]

  Python_constraint --> Resolver[Dependency resolver]
  Resolver -->|re-resolve dependencies using new Python patch| Uv_lock[uv.lock]

  Uv_lock --> Commit[Updated lockfile committed]
  Commit --> CI_checks[CI checks using Python >=3.14.4,<3.15]
  CI_checks --> Merge_queue[Mergify merge queue]
  Merge_queue --> Main_branch[main branch updated]

Loading

File-Level Changes

Change	Details	Files
Raise the minimum supported Python version and regenerate the lockfile accordingly.	Increase the requires-python floor from 3.14.3 to 3.14.4 while keeping the upper bound at <3.15 Regenerate uv.lock to align locked dependencies with the new Python version constraint and current dependency resolution	pyproject.toml uv.lock

Possibly linked issues

• #Dependency Dashboard: This merge-queue PR exists solely to merge Renovate PR chore(deps): update python to >=3.14.6,<3.15 #344, which implements the dashboard’s Python version update.

---

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...56178b2 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