New workflow_call workflow (.gitea/workflows/validate.yaml) that a consumer
repo can call to statically validate its renovate.json with
renovate-config-validator inside the official renovate/renovate image.
What it catches before Renovate runs (avoiding the dashboard-freeze class of
bug seen when an invalid config makes every extract fail):
- schema violations / unknown fields
- forbidden fields in customManagers (e.g. registryUrlsTemplate -
registryUrls is the only allowed form)
- malformed packageRules / matchStrings regexes
- bad extends / ignorePresets references
It does NOT run Renovate and does NOT touch dependencies - just parses the
config. Non-blocking when the caller has no renovate.json.
Usage in a repo (.gitea/workflows/renovate.yaml or a dedicated workflow):
jobs:
validate:
uses: perso/gitea-pipelines/.gitea/workflows/validate.yaml@main
Ajoute les tweaks manquants du modules/renovate/main.tf (tf-depl-kubernetes):
- semanticCommits: "enabled"
- binarySource: "install"
- printConfig: false
- packageRules: gitea-actions -> semanticCommitType "ci"
Pas d'autodiscover/autodiscoverFilter: le workflow renovate.yaml
passe deja RENOVATE_REPOSITORIES=github.repository pour scanner
uniquement le repo qui trigger la pipeline.
Hermes Agent
terraform