From 0c9d54daa10b4c142a5555529b53e90a960db57a Mon Sep 17 00:00:00 2001 From: Matt Norton Date: Fri, 21 Nov 2025 17:02:02 +0000 Subject: [PATCH 1/5] Update CONTRIBUTING.md using better sub-schema example (#5156) mypy was incorrectly used as an example of a sub-schema that has a standalone schema file. Switched to using hatch as an example instead. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2442a0737da..f93923989da 100644 --- a/CONTRIBUTING.md +++ b/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`. From ae64e29465f796515342639debaab4aead4bcadf Mon Sep 17 00:00:00 2001 From: Saucy9607 Date: Fri, 21 Nov 2025 11:02:15 -0600 Subject: [PATCH 2/5] Fix minItems for commitlint rules (#5154) This appears to have been changed upstream some time ago: https://github.com/conventional-changelog/commitlint/blob/b751b2999756c650b4b6131f99caa2c939d0a34b/%40commitlint/config-validator/src/commitlint.schema.json#L25 --- src/schemas/json/commitlintrc.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/schemas/json/commitlintrc.json b/src/schemas/json/commitlintrc.json index e9b0374a168..d0fc504c358 100644 --- a/src/schemas/json/commitlintrc.json +++ b/src/schemas/json/commitlintrc.json @@ -22,7 +22,7 @@ "description": "Value: the value for this rule" } ], - "minItems": 2, + "minItems": 1, "maxItems": 3, "additionalItems": false } From 6afe7dc03e74b26778de84267f06f6e53d1abd23 Mon Sep 17 00:00:00 2001 From: Kevin Goslar Date: Fri, 21 Nov 2025 11:02:31 -0600 Subject: [PATCH 3/5] Add Git Town schema to the catalog (#5157) * Add Git Town schema to the catalog * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> --- src/api/json/catalog.json | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/api/json/catalog.json b/src/api/json/catalog.json index 9c73ecade36..4b272ea2e55 100644 --- a/src/api/json/catalog.json +++ b/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", From 65b9e3046ea8a562922325cf9a76ac3ba299008b Mon Sep 17 00:00:00 2001 From: Brent Westbrook <36778786+ntBre@users.noreply.github.com> Date: Fri, 21 Nov 2025 12:03:56 -0500 Subject: [PATCH 4/5] Update ruff's JSON schema (#5158) This updates ruff's JSON schema to [762c44527ed78cd8d12c094b16a20a0ed15eab63](https://github.com/astral-sh/ruff/commit/762c44527ed78cd8d12c094b16a20a0ed15eab63) --- src/schemas/json/ruff.json | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/schemas/json/ruff.json b/src/schemas/json/ruff.json index ef81ba5adab..508278ce216 100644 --- a/src/schemas/json/ruff.json +++ b/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", From 6944911595508fbae92d9804bc04dc7586d44280 Mon Sep 17 00:00:00 2001 From: Marcell Vida <73988270+marcell-vida@users.noreply.github.com> Date: Fri, 21 Nov 2025 18:04:18 +0100 Subject: [PATCH 5/5] [bitrise-step] Add executables object (#5159) * [bitrise-step] Add executables object * Remove strict pattern matching from executables --- src/schemas/json/bitrise-step.json | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/schemas/json/bitrise-step.json b/src/schemas/json/bitrise-step.json index 6a72f8a98c1..6eb95304735 100644 --- a/src/schemas/json/bitrise-step.json +++ b/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,