chore(deps): bump pyright from 1.1.352 to 1.1.353 in /language-server

[dependabot[bot]]

Bumps pyright from 1.1.352 to 1.1.353.

Release notes

Sourced from pyright's releases.

Published 1.1.353

Breaking Changes:

• The CLI and language server versions of pyright now require a minimum node version of 14. Previously node 12 and 13 were supported.

Enhancements:

• Enabled PEP 705 and PEP 696 functionality without the use of enableExperimentalFeatures now that these PEPs are officially accepted.
• Improved support for instance variables whose type is declared in a metaclass. Pyright now honors this type and enforces type consistency in derived classes.

Bug Fixes:

• Fixed a bug that results in a false negative when a dundered method overrides a base class method of the same name and uses different parameter names along with different types.
• Fixed a bug that leads to a false positive error when a match statement is used in a loop and the subject expression is potentially narrowed as a result of the match statement.
• Added check for inappropriate use of Annotated passed as second argument to NewType call.
• Fixed a bug that results in a false positive error when expanding the type arguments to a TypeVarTuple under certain circumstances.
• Fixed a bug that results in incorrect type evaluation when an index expression is assigned a value within a doubly-nested loop under certain circumstances.
• Fixed a regression that caused the signature help provider to not display the __new__ method of a constructor if it is overloaded.
• Fixed hard-coded type information for module attribute __package__. It should be str | None rather than str.
• Fixed a bug in the isinstance type guard logic. It was not properly handling tuples that included unions.
• Fixed bug in signature help provider so str method docstrings are showed when called on LiteralString.
• Fixed a bug that results in incorrect type narrowing behavior for member access expressions under certain circumstances.
• Fixed bug that resulted in a false negative when a possibly-unbound variable is captured by an inner scope under certain circumstances.

Commits

• 114501e Published 1.1.353
• ab40240 Drop support for node 12 (#7375)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions[bot]]

Following are the schema changes in the new version. Make sure that those are reflected in LSP-pyright.sublime-settings and sublime-package.json files.

No updates done to sublime-package.json.