You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Renovate config validation fails in strict mode since Renovate 44.233 requires 'dependencyDashboard.labels' #3312
The "Validate Renovate configuration" step in vortex-test-common fails on every branch since Renovate 44.233.0 was published (2026-11-11, 16:20 UTC). The validator action installs the latest validator, and in --strict mode that version demands a config migration in the root renovate.json. The simple fix doesn't work on its own: the template's self-hosted Renovate on CircleCI is pinned to renovate/renovate:44.181.5, which rejects the migrated form.
main passed this job at 11:04 UTC, before the release, so it will fail on its next run.
Details
What fails
.github/workflows/vortex-test-common.yml runs suzuki-shunsuke/github-action-renovate-config-validator v2.4.1 with strict: true and no validator_version. It now resolves to Renovate 44.233.0, which reports:
In strict mode a necessary migration is an error, so the step exits with code 1. dependencyDashboardLabels is the only key it asks to migrate.
.github/workflows/update-dependencies.yml uses the same unpinned action, so it's likely affected too.
Why migrating alone breaks CircleCI
.circleci/update-dependencies.yml runs renovate/renovate:44.181.5 and validates the config with renovate-config-validator. Renovate 44.181.5 rejects the migrated form:
ERROR: Found errors in configuration
"message": "Configuration option `dependencyDashboard` should be boolean. Found: {\"labels\":[\"Dependencies\"]} (object)"
This was checked locally with @suzuki-shunsuke/renovate-config-validator@44.181.5 --strict against a config that has only the migrated key.
Options
Migrate renovate.json to dependencyDashboard.labels and bump renovate/renovate in .circleci/update-dependencies.yml to 44.233.0 or later, so both validators accept the same config. This is a template change, so installer snapshots need regenerating.
Pin validator_version on both GitHub Actions validator steps to the CircleCI image version, keeping the old key until the image is bumped. Renovate would need to keep the pin and the image in step.
Found on
#3281 (CI run 43102664794). That PR doesn't touch renovate.json or the workflows.
Activity
[#3312] Pinned the GitHub Actions Renovate run and config validators …
[#3312] Migrated Renovate config to 'dependencyDashboard.labels' and …