merge queue: embarking main (8980236), #336 and #337 together

[mergify]

✨ Pull request #336 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 (8980236), #336 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: 883aa46153af514968fc0f162a262b07769129e5
previous_failed_batches: []
pull_requests:
  - number: 337
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the development dependency on the 'ty' package to a newer patch version and refreshes the lockfile as part of an automated Renovate/Mergify merge-queue batch.

Entity relationship diagram for updated dev dependencies in pyproject.toml

erDiagram
    Project ||--o{ DependencyGroup : has
    DependencyGroup ||--o{ Package : includes

    Project {
        string name
        string requires_python
    }

    DependencyGroup {
        string group_name
        string file_pyproject_toml
    }

    Package {
        string name
        string version_spec
        boolean is_dev_dependency
    }

    Project ||--o{ Package : direct_dependency

    DependencyGroup_dev {
        string group_name_dev
    }

    Package_ruff {
        string name_ruff
        string version_spec_ge_0_15_9
        boolean is_dev_dependency_true
    }

    Package_ty_old {
        string name_ty
        string version_spec_ge_0_0_28
        boolean is_dev_dependency_true
    }

    Package_ty_new {
        string name_ty
        string version_spec_ge_0_0_29
        boolean is_dev_dependency_true
    }

    Project ||--o{ DependencyGroup : defines
    DependencyGroup_dev ||--o{ Package_ruff : contains
    DependencyGroup_dev ||--o{ Package_ty_new : contains

    Package_ty_old ||--|| Package_ty_new : replaced_by

Loading

File-Level Changes

Change	Details	Files
Bump the dev-only 'ty' Python dependency and synchronize the lockfile.	Increase the minimum required version of the 'ty' package in the dev dependency group from 0.0.28 to 0.0.29 in the project configuration. Regenerate or update the Python dependency lockfile to reflect the new dev dependency version constraint and maintain consistency with pyproject.toml.	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

[deepsource-io]

DeepSource Code Review

We reviewed changes in 8980236...f2aec8b 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:04p.m.	Review ↗
Secrets		Apr 9, 2026 9:04p.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.