chore(deps): update dependency ty to >=0.0.34#336
Conversation
|
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| Python | May 2, 2026 1:43a.m. | Review ↗ | |
| Secrets | May 2, 2026 1:43a.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.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
This is a straightforward dependency update (ty: 0.0.33 → 0.0.34) with no code changes. Reviewed by minimax-m2.5-20260211 · 256,213 tokens Reviewed by ling-2.6-1t-20260423:free · 343,447 tokens |
4067ff4 to
db46eb6
Compare
Merge Queue Status
This pull request spent 3 days 3 minutes 40 seconds in the queue, with no time running CI. Required conditions to merge
ReasonThe pull request #336 has been manually updated HintIf you want to requeue this pull request, you can post a |
db46eb6 to
7281388
Compare
Merge Queue Status
This pull request spent 35 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with pull requests ahead in queue: #348, #349 HintThere is nothing you can do for now. If the pull request ahead in the queue is merged, this pull request will become conflicting and you'll have to update it. |
|
Hey @renovate[bot], your pull request has been dequeued due to the following reason: CONFLICT_WITH_PULL_AHEAD. Sorry about that, but you can requeue the PR by using |
ff9b1fa to
81e77ad
Compare
Merge Queue Status
This pull request spent 1 day 17 hours 38 minutes 29 seconds in the queue, with no time running CI. ReasonThe pull request #336 has been manually updated HintIf you want to requeue this pull request, you can post a |
81e77ad to
12ee525
Compare
Merge Queue Status
This pull request spent 11 hours 58 minutes 22 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with pull requests ahead in queue: #348, #337, #344, #370, #371, #372, #373, #369 HintThere is nothing you can do for now. If the pull request ahead in the queue is merged, this pull request will become conflicting and you'll have to update it. |
|
Hey @renovate[bot], your pull request has been dequeued due to the following reason: CONFLICT_WITH_PULL_AHEAD. Sorry about that, but you can requeue the PR by using |
12ee525 to
30e0e6c
Compare
30e0e6c to
7956a78
Compare
7956a78 to
34793c4
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|



This PR contains the following updates:
>=0.0.28→>=0.0.34Release Notes
astral-sh/ty (ty)
v0.0.34Compare Source
Released on 2026-05-01.
Bug fixes
LSP server
Annotatedmetadata in semantic tokens (#24890)Core type checking
functools.partial(#24582)TypeIsassignability with gradual types (#24928)dict(**TypedDict)inTypedDictcontext (#24709)infer_variancefor legacyTypeVar(#24930)ParamSpec(#24927)UnionofTypedDictin various sites (#24958)Diagnostics
Performance
Contributors
v0.0.33Compare Source
Released on 2026-04-28.
Notable changes
ty now prefers the declared type of an annotated assignment in more situations (#24802).
Consider this example:
ty previously favored the inferred type of the right hand side expression when
thresholdandresultwere used. This is useful forthreshold, as it allows something likethreshold += 1to work without an error: we know thatthresholdcould later becomeNone, but right now, we see that it is anint. However, forresult, the inferred type isUnknown. This is not a useful type and it can lead to false negatives. Starting with this release, ty will therefore preferthe declared type if the inferred and declared types are mutually assignable. In the above example,
thresholdwill still be inferred asint(or ratherLiteral[1]), butresultwill now be inferred asstr. If you previously addedcasts to work around this behavior, you should be able to remove them after upgrading.Bug fixes
LSP server
Core type checking
finallyblocks where alltry/exceptblocks are terminal (#24882)ClassVarvs instance-attribute overrides (#24767)Unpack[...](#24868)Callabletype context (#24317)**unpacking ofTypedDictin dict-literal assignments (#24703)Unpack[TypedDict]in**kwargssignatures (#24653)[*xs]as an irrefutable pattern when matching onSequence(#24787)Diagnostics
invalid-return-typediagnostics,invalid-yielddiagnostics, attribute assignment diagnostics (#24770, #24771)dictassignment error diagnostics (#24768)invalid-keydiagnostics for unions of TypedDicts (#24693)invalid-type-formdiagnostics for PEP-613 type alias values (#24760)Performance
Other changes
Contributors
v0.0.32Compare Source
Released on 2026-04-20.
Bug fixes
__get__usesConcatenateself-type and wraps a__call__(#24692)Callabletype context (#24661)LSP server
@overload-decorated function has no docstring (#23920)Core type checking
ifstatements in TypedDict bodies (#24702)@disjoint_baseon TypedDicts and Protocols (#24671)@dataclass_transform-decorated class to have dataclass-like semantics if it hastypein its MRO (#24679)Neversetters or deleters (#24510)Diagnostics
Performance
Contributors
v0.0.31Compare Source
Released on 2026-04-15.
Bug fixes
namedtuple(typename=T, field_names=x, **{})(#24641)Enum(...)names (#24638)Enum(value=...)(#24639)invalid-keyfix doesn't converge, andoverride-of-final-methodproduces invalid syntax (#24649)ty:ignorecomments inserted by--add-ignorefor diagnostics starting on the same line (#24651)CLI
--fixmode to enable auto-fix for diagnostics (#24097)Performance
Core type checking
NamedTuplefield conflicts (#24542)EnumMeta.__call__for enum constructor signatures (#24513)Contributors
v0.0.30Compare Source
Released on 2026-04-13.
As of v0.0.30, ty no longer unions
Unknowninto most inferred types of unannotated attributes. For example:In previous versions,
reveal_type(Foo().value)would have includedUnknown, so the assignment to"x"would not have been flagged. Since this can affect inferred attribute types throughout a codebase, upgrading may lead to both new and resolved diagnostics. Initializers ofNoneand other non-literal singleton types remain exceptions. See #24531 for details.Bug fixes
ParamSpecinConcatenateprefixes (#24474)Callabletypes (#24497)TYPE_CHECKINGstate from outer blocks (#24470)__init_subclass__calls (#24541)type[T]to a metaclass (#24515)ParamSpec-specialized class calls (#24399)TypedDictfield types as type context to inform the inference of arguments passed toTypedDictconstructors (#24422)LSP server
typingandcollectionshigher than third party re-exports (#23643)TypedDictconstructor support in the LSP by synthesizing__init__(#24476, #24522, #24535)infosubdiagnostics in LSP diagnostic messages (#24328)Diagnostics
Core type checking
Enum(...)syntax (#23602, #24570, #24571)Finalvariable assignments in__post_init__(#24529)type[...]annotations, e.g.type["MyClass"](#24518)__init_subclass__ = None(#24543)TypeGuardandTypeIsnarrowing for unbound method calls (#24612)list[int][0]leads to 1 diagnostic, rather than 2 (#24354)dataclass_transformmetadata from metaclass bases (#24615)Noneaccessors in manual property construction (#24492)Finalattributes (#24508)TypedDictunpacking (#24446)strconstructor (#24514)Unknowninto types of un-annotated attributes (#24531)super()in metaclass methods (#24483)Concatenatetype-expression parsing (#24172)if TYPE_CHECKINGblock (#24394)Contributors
v0.0.29Compare Source
Released on 2026-04-05.
Bug fixes
dataclasses.fieldif it's not infield_specifiers(#24397)environment.python-versionvalues in configuration files (#24402)requires-python(#24401)Core type checking
types.new_class(#23144)withstatement (#24395)__new__and metaclass__call__return types (#24357)Contributors
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.