Update dependency ty to >=0.0.37

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ty (changelog)	>=0.0.36 → >=0.0.37

---

Release Notes

astral-sh/ty (ty)

v0.0.37

Compare Source

Released on 2026-05-16.

Bug fixes

• Avoid unsound not in narrowing (#​25161)
• Fix async iteration over narrowed typevars (#​25155)
• Fix panic in double-inference for single starred positional TypedDict (#​25176)
• Fix panic in disjoint base check (#​25187)
• Fix panic in recursive binary inference (#​25189)
• Fix panic in cyclic __new__ (#​25185)
• Fix panic in reveal_protocol, reveal_mro, etc. with keyword arguments (#​25179)
• Fix panic in imported overload definition (#​25168)

LSP server

• Don't show argument inlay for case-insensitive matches or prefix/suffixes (#​25174)
• Reduce CPU usage of the LSP when switching between large changesets (#​25142)

Core type checking

• Avoid enforcing __new__ with custom metaclasses (#​25180)
• Make overload public type reachability-aware (#​25171)
• Only specialized types of generic class instances should influence variance (#​25124)
• Preserve ParamSpec argument context through wrapper calls (#​24934)
• Support partially specialized type context for collection literals (#​24506)

Contributors

• @​RasmusNygren
• @​MichaReiser
• @​charliermarsh
• @​ibraheemdev

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[semanticdiff-com]

Review changes with  

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-16 09:28 UTC · Rule: Python Dependency Updates
• ✅ Checks started · on draft merge queue: embarking main (28b3111) and #1875 together #1876
• 🚫 Left the queue — 2026-05-16 09:33 UTC · at 54e7279cf56dd52aaa696864e21e8611c2c6a676

This pull request spent 4 minutes 16 seconds in the queue, including 3 minutes 59 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• 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

Reason

The merge conditions cannot be satisfied due to failing checks

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-20 02:50 UTC · Rule: Python Dependency Updates
• ✅ Checks started · on draft merge queue: embarking main (8f7fb8c) and #1875 together #1913
• ❌ Checks failed
• 🚫 Left the queue — 2026-05-20 02:53 UTC · at d6a762e53068c77c55c2733791e5918054e1732b

This pull request spent 3 minutes 57 seconds in the queue, including 3 minutes 26 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• 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

Reason

The merge conditions cannot be satisfied due to failing checks

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

[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]

Hi @renovate[bot], Your PR is in conflict and cannot be merged.

[mergify]

👋 renovate[bot] your PR is conflicting and needs to be updated to be merged