Update dependency pyright to ^1.1.386

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pyright (source)	^1.1.384 -> ^1.1.386

---

Release Notes

Microsoft/pyright (pyright)

v1.1.386: Published 1.1.386

Compare Source

Bug Fixes:

• Fixed issue that results in non-deterministic false positive error, often relating to the "awaitable" check.
• Fixed bug that results in a false positive error when using a traditional generic type alias defined with a "naked" type variable surrounded by Annotated within a Python 3.12 type statement.
• Fixed a bug that leads to a false positive when using asssert_type with a **kwargs parameter that is annotated with an unpacked TypedDict.
• Fixed recent regression that results in a spurious type error when accessing an instance variable self.x if x has the type of a class-scoped type variable with a default value.
• Fixed a recent regression that results in false positive errors under certain circumstances that involve assignability checks for two callables that involve a *args: *tuple[] parameter.
• Fixed bug that results in a false positive when resolving a multi-part import target that involves a circular dependency.
• Fixed regression that results in a false positive error (and an error that is reported at a bogus location) when overriding a dataclass field with a converter.
• Fixed bug in constraint solver that resulted in behavior that differed depending on the order of methods in a protocol.
• Fixed a bug that results in a spurious error when specializing an old-style generic type alias whose type is defined as a new-style type alias that has multiple type parameters, only some of which are used in its type definition.
• Fixed bug that leads to incorrect type narrowing in the negative ("else") case when using isinstance with a filter type that is typed as type[X].
• Fixed bug that results in a false negative when the specialization of a ParamSpec results in a signature that has a duplicate parameter name where one parameter has a default value and the other does not.

Enhancements:

• Added a limit to the number of typed declarations that will be evaluated for a single symbol. This mitigates performance issues with code that redeclares a symbol hundreds or thousands of times.
• Updated support for "closed" TypedDict to match latest updates to PEP 728.
• Enhanced the type(y) == x type guard logic to support the case where y is declared as a type variable with an upper bound that overlaps with the type of x.
• Updated typeshed stubs to the latest version.
• Updated toml parser library to support toml 1.0.0 syntax.
• Removed the limitation that the "ignore" setting in a config file must be relative to the project root.

v1.1.385: Published 1.1.385

Compare Source

Bug Fixes:

• Fixed bug that leads to a false positive error when using Literal[] in a value expression (not a type expression) with an unpack operator.
• Fixed a recent regression that results in a false positive in cases where a dataclass field has a default value where the expression requires bidirectional type inference for proper type evaluation.
• Fixed recent regression that results in a false negative when calling a constructor for a class with a custom metaclass with a __call__ method that has an unannotated return type if the arguments passed to the constructor are incorrect.
• Fixed bug that results in a false positive when a NamedTuple field uses ... as a default value in a stub file.
• Fixed recent regression that leads to a false positive error when assigning a generic method within a class body.
• Fixed recent regression that results in a false negative when calling a function with an *args parameter annotated with an unpacked tuple.
• Fixed bug that results in false positive error when a dataclass field is annotated with a class-scoped type variable and includes a default value whose type require bidirectional type inference.
• Fixed bug that results in incorrect type evaluation and a false negative when accessing an attribute through a TypeVar with an upper bound.
• Fixed bug that results in false positive error regarding a __bool__ method for a value used in an operand for an or or and operator.

Enhancements:

• Added check for alias keyword argument in a dataclass_transform field definition call to ensure that it's a valid Python identifier.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.