[pull] master from SchemaStore:master - #577
Merged
Merged
Conversation
Co-authored-by: btea <btea@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Now we've released Renovate 44, we'll store the 43.288.0 JSON schema as an older version for folks to access. Co-authored-by: Claude Opus 4.8 (1M context) <jamie.tanna+claude-code@mend.io>
…6145) `otel*.yaml` / `otel*.yml` match `otel-collector.yaml` — the conventional name for an OpenTelemetry **Collector** config. That is a different format from the SDK declarative configuration this schema describes, with no root `file_format` key, so those files get a spurious error-severity `Missing property "file_format"`. By code search that one filename is ~2,000 files. `#6143` has the reproduction. ## Why removal rather than a narrower glob `otel*` was not tracking a convention. From open-telemetry/opentelemetry-configuration#468, where this entry was proposed: > I set file match to: `opentelemetry*.yaml`, `opentelemetry*.yml`, `otel*.yaml`, `otel*.yml` … This means we should adjust our examples to follow this format. open-telemetry/opentelemetry-configuration#488 then renamed the examples to fit, so they are downstream of the pattern rather than evidence for it. The format has no filename convention otherwise — the spec fixes only the extension. The candidate replacement `otel-sdk*` is ~11 files across public GitHub against ~2,000, and two of those are the renamed examples. Happy to add `otel-sdk*.yaml` / `otel-sdk*.yml` if you would rather keep them matched — it carries no Collector-collision risk — but it looked like codifying a name almost nobody uses, so I would rather you called it. Losing the inference follows `#5557`; users opt back in with a `$schema` modeline or by selecting the schema manually. ## What this does not fix, and an open question The surviving `opentelemetry*` patterns are no better than the two this removes. By code search they match roughly 1,260 files — ~566 `opentelemetry.yaml`, ~116 `.yml`, ~450 `opentelemetry-collector.yaml`, ~74 `opentelemetry-values.yaml`, ~40 `opentelemetry-config.yaml` — of which **one** contains `file_format`, the key this schema requires at its root. At least 29 are Kubernetes `kind: OpenTelemetryCollector` operator manifests; ~89 are Helm values files. In the entry's defence, declarative configuration was only recently marked stable, so that near-zero count reflects nascent adoption rather than a wrong idea — the glob looks premature rather than misconceived. I have kept this diff to what `#6143` proposed rather than widening it unilaterally. We could also make it `"fileMatch": []` instead — the remedy `CONTRIBUTING.md` names and `#5556` used, leaving the schema registered and manually selectable — if you would rather fix both halves at once. A specific pattern can be added later once a filename convention exists. There is also a cheaper durable fix upstream, too: renaming the examples to `opentelemetry-*.yaml` keeps them matched by the surviving patterns, and #488 is the precedent for exactly that move. cc @jack-berg, who added this entry in `#5436`. Closes #6143.
Add JSONC format file matches for oxlint and oxfmt
This updates ruff's JSON schema to [4a437b093417a22abecc168cc186ef58ca48c0fc](astral-sh/ruff@4a437b0)
…6149) * chore(tsbuild): add TypeScript build schema and configuration files * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Potential fix for pull request finding Forgot to add the tsconfig.json entry in the fileMatch Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * chore: move entry to be alphabetically positioned --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Register three externally hosted skill-map schemas: the plugin extension manifest, the provider node-kind descriptor, and the per-project settings file (.skill-map/settings.json and its .local partner). The schema files are served from https://skill-map.ai. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )