⬆️ deps: Update dependency ty to >=0.0.75

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ty (changelog)	>=0.0.74 → >=0.0.75

---

Release Notes

astral-sh/ty (ty)

v0.0.75

Compare Source

Released on 2026-08-26.

Preview features

• Initialize PEP 723 script environments in the CLI (#​27544)
• Refresh PEP 723 script environments in watch mode (#​27617)
• Run PEP 723 script synchronization on bounded workers (#​27615)

Bug fixes

• Specialize Self bounds of inherited methods (#​27990)

LSP server

• Add "Go to Definition" support for pytest fixtures (#​27444)

Documentation

• Fix documented Python package build command (#​4384)
• Link untyped-call tracking issue in migration guide (#​4382)

Library support

• Resolve imported pytest fixture exposures (#​27539)
• Resolve installed core pytest fixture providers (#​27770)
• Resolve pytest fixtures through conftest (#​27540)

Diagnostics

• Add more autofixes (#​28029)
• Add a dedicated missing-slot diagnostic (#​28039)
• Explain missing storage for declared slotted attributes (#​27969)
• Improve diagnostic spans for unpacked variable assignments (#​28041)

Core type checking

• Account for known subclasses in equality inference (#​28005)
• Expand ParamSpec signatures inferred from bound receivers (#​28020)
• Fix Self binding in ParamSpec protocols (#​28016)
• Fix TypedDict variance inference (#​28052)
• Fix unsound narrowing through branch-assigned conditions (#​28006)
• Ignore inconsistent binding decorators on overloads (#​28036)
• Infer yield from send/return types from the iterator returned by __iter__ (#​27987)
• Infer tuple type parameters from union arguments (#​28062)
• Infer variance through nonrecursive protocol references (#​28065)
• Preserve bounds of non-literal metaclasses (#​28046)
• Preserve correlated generic-call inference (#​28043)
• Preserve invariant materialization constraints (#​28047)
• Recover bare TypeVarTuples in tuple annotations (#​27950)
• Reject fixed tuples for non-inferable TypeVarTuples (#​27943)
• Reject incompatible constructor context for variadic packs (#​27966)
• Support mixed gradual tuple assignability with TypeVarTuple (#​27957)
• Support tagged union with multiple tags per type (#​27984)
• Sync vendored typeshed stubs (#​28035). Typeshed diff
• Treat typing.Union as a class on Python 3.14+ (#​28003)
• Validate generic protocol variance (#​27531)
• collections.abc.Callable is an instance of type (#​27991)

Contributors

• @​sharkdp
• @​jelle-openai
• @​marcelo-souzaf
• @​AlexWaygood
• @​krzkaczor
• @​carljm
• @​charliermarsh
• @​lerebear
• @​MichaReiser

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml

Artifact update for ty resolved to version 0.0.77, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.0.75
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/