Renovate Config Validator

How to use this developer tool

1. Paste your input or load the provided sample.
2. Adjust any options shown beneath the editor.
3. Select Validate Config or press Ctrl/Cmd + Enter.
4. Review the summary, diagnostics, and exported output before committing it.

What this developer tool does

Known configuration fields are checked by expected type. Each packageRules entry is inspected for at least one matcher and one action, while obvious deprecated keys produce warnings.

A local structural pass is useful before committing, but only Renovate itself can validate every preset, manager, datasource, and hosted-platform interaction.

Example

Try the sample input built into the page. The result uses the same validation and export path as pasted content.

{"extends":["config:recommended"],"schedule":["before 6am on monday"],"packageRules":[{"matchUpdateTypes":["minor","patch"],"groupName":"non-major updates"}]}

Use cases

• Prepare repository configuration during project setup.
• Review a proposed change before opening a pull request.
• Turn issue or workflow data into a consistent, copy-ready artifact.

Tips for reliable output

• Start with the sample to confirm the expected shape.
• Keep repository names, paths, and owner handles exact.
• Read warnings even when output is generated.
• Commit configuration changes in a separate pull request when practical.
• Test critical automation on a non-production branch first.

Processing details

The validator accepts strict JSON. It reports unknown top-level fields as review items rather than errors because Renovate adds options over time.

Remote presets are not fetched, and regex manager patterns are not executed against repository files.