Files
renovate/tools/docs
Jamie Tanna d4074b4ffb fix(json-schema): don't treat a map of values as a nested config (#46673)
Options like `secrets`, `registryAliases` and `productLinks` are a map
of user-chosen keys to simple values, but when we generate the JSON
Schema, we use a `$ref` to the root schema, in a similar way to options
that do have a nested Renovate config, like `force` or
`onboardingConfig`.

That means the keys of the map are validated as if they were config
options, so a perfectly valid config is reported as an error:

```yaml
secrets:
  # must be boolean
  enabled: a-secret

registryAliases:
  # must be array
  labels: https://example.com
```

As we already have `additionalProperties` defined, we can use these to
document the format of the body, instead of treating it as a Renovate
schema.

Co-authored-by: Claude Opus 5 <jamie.tanna+claude-code@mend.io>
2026-10-08 13:09:29 +00:00
..