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

[mergify]

✨ Merge queue reset: an external action moved the base branch head to 8980236. The pull request #337 has been re-embarked. ✨

Branch main (4e35877), #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: a8d0d6245fa987bd1191644ca84436f6d9b5929c
previous_failed_batches: []
pull_requests:
  - number: 337
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Python development dependency ty to a newer patch version and refreshes the corresponding lockfile, as part of a merge-queue speculative PR created by Mergify for Renovate’s dependency update (#337).

Sequence diagram for merge queue speculative dependency update PR

sequenceDiagram
    actor RenovateBot
    participant GitHubRepo
    participant Mergify
    participant MergeQueue
    participant CI as GitHubActionsCI

    RenovateBot->>GitHubRepo: Create PR_337 updating_dev_dependency_ty_to_0_0_29
    GitHubRepo-->>CI: Trigger_Check_Dependency_Compatibility
    CI-->>GitHubRepo: Report_success_for_Check_Dependency_Compatibility

    GitHubRepo-->>Mergify: Notify_PR_337_status_updates
    Mergify->>MergeQueue: Enqueue_PR_337_in_Python_Dependency_Updates_queue

    MergeQueue->>GitHubRepo: Create_speculative_PR_merge_queue_PR
    GitHubRepo-->>CI: Run_Test_Image_API_Test_and_Mergify_Merge_Protections
    CI-->>GitHubRepo: Report_status_of_required_checks

    GitHubRepo-->>Mergify: Notify_speculative_PR_check_results
    Mergify->>MergeQueue: Decide_merge_or_requeue_PR_337
    Mergify-->>GitHubRepo: Close_speculative_merge_queue_PR_when_complete

Loading

File-Level Changes

Change	Details	Files
Bump the ty development dependency and align the lockfile with the new version.	Increase the ty dev dependency constraint from 0.0.28 to 0.0.29 in the project configuration. Regenerate/update the uv.lock file so that it is consistent with the new ty version and dependency graph.	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 4e35877...be7e80e 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 6, 2026 9:02p.m.	Review ↗
Secrets		Apr 6, 2026 9:02p.m.	Review ↗

[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

[mergify]

Merge queue reset: an external action moved the base branch head to 8980236