chore(deps): update dependency ty to >=0.0.19,<0.0.20

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ty (source)	feature-test	patch	>=0.0.18,<0.0.19 → >=0.0.19,<0.0.20

---

Release Notes

astral-sh/ty (ty)

v0.0.19

Compare Source

Released on 2026-02-26.

Bug fixes

• Fix panic in diagnostic rendering when attempting to render a code frame pointing to leading whitespace (#​23458)
• Fix panics and incorrect inference stemming from incorrectly considering overloads in another file as being associated with a function in the file being checked (#​21977)
• Fix panic when attempting to narrow the type of a dictionary key that was assigned using a multi-target assignment, e.g. x = y = {"a": 1} (#​23523)
• Fix infinite hang on mutually recursive TypeAliasType definitions (#​23397)

LSP server

• Fix inlay hints for starred unpacking targets (#​23454)

Core type checking

• Fix assignability, subtyping and equivalence checks relating to typing.Generator prior to Python 3.13 (#​23386)
• Understand that a scope's control flow terminates after await foo() if foo returns typing.Awaitable[typing.Never] or similar (#​23479)
• Implement stricter handling of calls to instances of type[T] types (#​23472)
• Support basic type narrowing for case {...}: patterns in match statements (#​23462)
• Fix bugs that could manifest in incorrect overload evaluation, false-positive complaints regarding assert_type calls or false-positive redundant-cast diagnostics by reimplementing the equivalence type relation as mutual subtyping of top and bottom materializations (#​23428)
• Fix equality and __contains__ narrowing with PEP-695 type aliases (#​23545)
• Support _value_ annotations on enum classes (#​22228)

Improvements to diagnostics

• Improve diagnostics when attempting to specialize non-generic types (#​23516)
• Render subdiagnostics when --output-format=github is specified (#​23455)

Performance

• Add a cached method for calculating the intersection of two types (#​23547)
• Add a cached method for calculating the union of two types (#​23565)
• Reduce the threshold above which Literal types in unions are upcasted to nominal-instance types in situations where the union type is recursively defined (#​23521)
• Control flow: isolate the calculation of "loop header reachability" in a dedicated, cached function (#​23520)

Contributors

• @​AlexWaygood
• @​silamon
• @​ibraheemdev
• @​Hugo-Polloli
• @​charliermarsh
• @​knutwannheden
• @​oconnor663
• @​carljm
• @​mtshiba

---

Configuration

📅 Schedule: 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 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: pixi.lock

ExecError: Command failed: pixi lock --no-progress --color=never --quiet
Error:   × failed to solve requirements of environment 'dev' for platform 'osx-arm64'
  ├─▶   × failed to solve the environment
  │   
  ╰─▶ Cannot solve the request because of: libmambapy >=2.4.0,<3 cannot be
      installed because there are no viable options:
      └─ libmambapy 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 |
      2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 |
      2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.5.0 |
      2.5.0 | 2.5.0 | 2.5.0 | 2.5.0 | 2.5.0 would require
         └─ python 3.10.* *_cpython, for which no candidates were found.
      The following packages are incompatible
      ├─ libmambapy >=2.4.0,<3 can be installed with any of the following
      options:
      │  └─ libmambapy 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 | 2.4.0 |
      2.4.0 | 2.5.0 | 2.5.0 | 2.5.0 would require
      │     └─ python 3.14.* *_cp314, which can be installed with any of the
      following options:
      │        └─ python 3.14.0 | 3.14.0 | 3.14.0 | 3.14.0 | 3.14.1 | 3.14.2 |
      3.14.2 | 3.14.2 | 3.14.3 | 3.14.3 | 3.14.3
      └─ ty >=0.0.19,<0.0.20 cannot be installed because there are no viable
      options:
         └─ ty 0.0.19 would require
            └─ python_abi 3.10.* *_cp310, which cannot be installed because
      there are no viable options:
               ├─ python_abi 3.10, which conflicts with the versions reported
      above.
               ├─ python_abi 3.10, which conflicts with the versions reported
      above.
               ├─ python_abi 3.10, which conflicts with the versions reported
      above.
               ├─ python_abi 3.10, which conflicts with the versions reported
      above.
               ├─ python_abi 3.10, which conflicts with the versions reported
      above.
               ├─ python_abi 3.10 would constrain
               │  └─ python 3.10.* *_cpython, which conflicts with any
      installable versions previously reported
               └─ python_abi 3.10 would require
                  └─ python 3.10.*, for which no candidates were found.