[pull] master from SchemaStore:master

CONTRIBUTING.md

@@ -695,7 +695,7 @@ Often, it is useful to extract a subschema into its own file. This can make it e
 A subschema should be extracted to its own file based on the following rules:
 
 - If a schema represents an existing project that could be its own file, then simply use that file for the "subschema". In other places, `$ref` that file where appropriate.
-  - For example, [mypy](https://mypy-lang.org) reads configuration from both `mypy.ini` and `pyproject.toml`'s `tool.mypy` key. Because `mypy.ini` is its own file, then name the schema `mypy.json` like you usually would.
+  - For example, [hatch](https://hatch.pypa.io/latest/) reads configuration from both `hatch.toml` and `pyproject.toml`'s `tool.hatch` key. Because `hatch.toml` is its own file, then name the schema `hatch.json` like you usually would.
   - Same with [Prettier](https://prettier.io). It reads from `.prettierrc.json` (among other files) and `package.json`'s `prettier` key.
 - If the schema cannot be its own file, then extracting the subschema may be an improvement
   - For example, [Poetry](https://python-poetry.org) reads configuration _only_ from `pyproject.toml`'s `tool.poetry` key. Because the Poetry subschema is relatively complex and a large project, it has been extracted to its own file, `partial-poetry.json`.

src/api/json/catalog.json

@@ -8790,6 +8790,12 @@
       ],
       "url": "https://raw.githubusercontent.com/airbytehq/airbyte/refs/heads/master/airbyte-ci/connectors/metadata_service/lib/metadata_service/models/generated/ConnectorMetadataDefinitionV0.json"
     },
+    {
+      "name": "git-town.toml",
+      "description": "Git Town configuration file",
+      "fileMatch": ["git-town.toml"],
+      "url": "https://raw.githubusercontent.com/git-town/git-town/refs/heads/main/docs/git-town.schema.json"
+    },
     {
       "name": "Jarl",
       "description": "Configuration for R linter",

src/schemas/json/bitrise-step.json

@@ -80,6 +80,17 @@
       "additionalProperties": false,
       "type": "object"
     },
+    "ExecutableModel": {
+      "properties": {
+        "storage_uri": {
+          "type": "string"
+        },
+        "hash": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "GoStepToolkitModel": {
       "required": ["package_name"],
       "properties": {
@@ -199,6 +210,13 @@
             "type": "object"
           },
           "type": "array"
+        },
+        "executables": {
+          "description": "Platform-specific executable binaries",
+          "type": "object",
+          "additionalProperties": {
+            "$ref": "#/definitions/ExecutableModel"
+          }
         }
       },
       "additionalProperties": false,

src/schemas/json/commitlintrc.json

@@ -22,7 +22,7 @@
               "description": "Value: the value for this rule"
             }
           ],
-          "minItems": 2,
+          "minItems": 1,
           "maxItems": 3,
           "additionalItems": false
         }

src/schemas/json/ruff.json

@@ -54,7 +54,7 @@
       "deprecated": true
     },
     "extend": {
-      "description": "A path to a local `pyproject.toml` file to merge into this\nconfiguration. User home directory and environment variables will be\nexpanded.\n\nTo resolve the current `pyproject.toml` file, Ruff will first resolve\nthis base configuration file, then merge in any properties defined\nin the current configuration file.",
+      "description": "A path to a local `pyproject.toml` or `ruff.toml` file to merge into this\nconfiguration. User home directory and environment variables will be\nexpanded.\n\nTo resolve the current configuration file, Ruff will first load\nthis base configuration file, then merge in properties defined\nin the current configuration file. Most settings follow simple override\nbehavior where the child value replaces the parent value. However,\nrule selection (`lint.select` and `lint.ignore`) has special merging\nbehavior: if the child configuration specifies `lint.select`, it\nestablishes a new baseline rule set and the parent's `lint.ignore`\nrules are discarded; if the child configuration omits `lint.select`,\nthe parent's rule selection is inherited and both parent and child\n`lint.ignore` rules are accumulated together.",
       "type": ["string", "null"]
     },
     "extend-exclude": {
@@ -693,6 +693,10 @@
           "type": ["integer", "null"],
           "format": "uint",
           "minimum": 0
+        },
+        "type-checking-imports": {
+          "description": "Whether to include imports that are only used for type checking (i.e., imports within `if TYPE_CHECKING:` blocks).\nWhen enabled (default), type-checking-only imports are included in the import graph.\nWhen disabled, they are excluded.",
+          "type": ["boolean", "null"]
         }
       },
       "additionalProperties": false
@@ -3178,6 +3182,7 @@
         "PLR170",
         "PLR1702",
         "PLR1704",
+        "PLR1708",
         "PLR171",
         "PLR1711",
         "PLR1714",