1.2.78

• chore: update pyright 1.1.355

1.2.77

• chore: update pyright 1.1.354

1.2.76

• chore: update pyright 1.1.353

1.2.75

• chore: update pyright 1.1.352

1.2.74

• chore: update pyright 1.1.351

1.2.73

• chore: update pyright 1.1.350

1.2.72

• chore: update pyright 1.1.349

1.2.71

• chore: update pyright 1.1.348

Breaking Changes:

Many pyright users have requested finer-grained control over diagnostics — especially for diagnostics that were previously lumped under the catch-all rule reportGeneralTypeIssues. I was hesitant to do this because it is a breaking change and could be disruptive for some pyright users. However, the time has come to make this change.

The list of new diagnostic rules includes:

• reportAbstractUsage
• reportArgumentType
• reportAssertTypeFailure
• reportAssignmentType
• reportAttributeAccessIssue
• reportCallIssue
• reportInconsistentOverload
• reportIndexIssue
• reportInvalidTypeArguments
• reportInvalidTypeForm
• reportNoOverloadImplementation
• reportOperatorIssue
• reportPossiblyUnboundVariable
• reportRedeclaration
• reportReturnType
• reportUnusedExcept

Refer to the configuration documentation for more details about each of these.

This is a breaking change for code bases that were previously overriding the diagnostic severity for reportGeneralTypeIssues in the config file, in file-level pyright comments or in # type: ignore or # pyright: ignore comments. You will need to update your configuration settings and comments to use the new diagnostic rule names.

1.2.70

• chore: update pyright 1.1.347

1.2.69

• chore: update pyright 1.1.346