Skip to content

ci: add reusable Renovate config validation workflow - #12

Merged
00o-sh merged 1 commit into
mainfrom
claude/renovatebot-pre-commit-hooks-t1ruu1
Aug 13, 2026
Merged

ci: add reusable Renovate config validation workflow#12
00o-sh merged 1 commit into
mainfrom
claude/renovatebot-pre-commit-hooks-t1ruu1

Conversation

@00o-sh

@00o-sh 00o-sh commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

What & why

Adds a shared reusable-renovate-config workflow that runs renovate-config-validator --strict over a caller-supplied list of config files (defaults to the fork's root renovate.json).

Until now, only unabandoned/renovate-config validated its preset in CI — the individual forks' renovate.json files were unvalidated. Since these repos are largely bot- and Claude-authored, a malformed renovate.json could slip in and silently halt Renovate for that fork. This gives every fork a cheap, tokenless guard (the validator checks file structure via npx; it does not resolve the remote preset, so no RENOVATE_TOKEN/GITHUB_COM_TOKEN is required).

This repo also dogfoods the workflow against its own renovate.json via a local ./-ref caller, matching the existing commitlint self-caller pattern.

Matching caller branches are opened across the onboarded forks and renovate-config.

Type of change

  • fix / feat / perf — consumer-facing
  • deps — dependency update (add the security label if it fixes a CVE)
  • chore / ci / build / docs / test / refactor — maintenance

Checklist

  • Commits follow Conventional Commits (commitlint passes)
  • npm test passes on Node 20 / 22 / 24 — N/A (CI-config-only change; no package here)
  • No new runtime dependency
  • Dev tree kept lean (validator runs via npx in CI; nothing added to any tree)

Generated by Claude Code

Adds a reusable workflow that runs renovate-config-validator --strict on
a caller-supplied set of config files (defaults to renovate.json), plus a
self-caller so this repo dogfoods it against its own renovate.json.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants