[create-pull-request] automated change (#44)

Co-authored-by: henryiii <4616906+henryiii@users.noreply.github.com>

pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "validate-pyproject-schema-store"
-version = "2024.05.13"
+version = "2024.05.20"
 authors = [
   { name = "Henry Schreiner", email = "henryfs@princeton.edu" },
 ]

src/validate_pyproject_schema_store/resources/pyright.schema.json

@@ -66,8 +66,8 @@
       "$id": "#/properties/strict",
       "type": "array",
       "title": "Files and directories that should use \"strict\" type checking rules",
-      "description": "Paths of directories or files that should use \"strict\" analysis if they are included. This is the same as manually adding a `# pyright: strict` comment. In strict mode, most type-checking rules are enabled. Refer to this table for details about which rules are enabled in strict mode. Paths may contain wildcard characters: `**` (a directory or multiple levels of directories), `*` (a sequence of zero or more characters), or `?` (a single character).",
-      "x-intellij-html-description": "Paths of directories or files that should use &quot;strict&quot; analysis if they are included. This is the same as manually adding a <code># pyright: strict</code> comment. In strict mode, most type-checking rules are enabled. Refer to this table for details about which rules are enabled in strict mode. Paths may contain wildcard characters: <code>**</code> (a directory or multiple levels of directories), <code>*</code> (a sequence of zero or more characters), or <code>?</code> (a single character).",
+      "description": "Paths of directories or files that should use \"strict\" analysis if they are included. This is the same as manually adding a `# pyright: strict` comment. In strict mode, most type-checking rules are enabled. Paths may contain wildcard characters: `**` (a directory or multiple levels of directories), `*` (a sequence of zero or more characters), or `?` (a single character).",
+      "x-intellij-html-description": "Paths of directories or files that should use &quot;strict&quot; analysis if they are included. This is the same as manually adding a <code># pyright: strict</code> comment. In strict mode, most type-checking rules are enabled. Paths may contain wildcard characters: <code>**</code> (a directory or multiple levels of directories), <code>*</code> (a sequence of zero or more characters), or <code>?</code> (a single character).",
       "items": {
         "$id": "#/properties/strict/items",
         "type": "string",
@@ -248,14 +248,14 @@
       "$ref": "#/definitions/diagnostic",
       "title": "Controls reporting of type expressions that use an invalid form",
       "description": "Generate or suppress diagnostics for type annotations that use invalid type expression forms or are semantically invalid.",
-      "default": "warning"
+      "default": "error"
     },
     "reportMissingTypeStubs": {
       "$id": "#/properties/reportMissingTypeStubs",
       "$ref": "#/definitions/diagnostic",
       "title": "Controls reporting of imports that cannot be resolved to type stub files",
       "description": "Generate or suppress diagnostics for imports that have no corresponding type stub file (either a typeshed file or a custom type stub). The type checker requires type stubs to do its best job at analysis.",
-      "default": "warning"
+      "default": "none"
     },
     "reportImportCycles": {
       "$id": "#/properties/reportImportCycles",