fix(renovate): migrate config off keys removed in Renovate 41
Why now
This project was created 2026-07-21 — one day after the last scheduled Renovate run (2026-07-20) — so Renovate has never visited it. That explains the absence of a Dependency Dashboard here; it is not a failure, just a repo the bot hasn't reached yet.
It would fail on its first visit. regexManagers and fileMatch were both removed in Renovate 41, and the runner executes 43.272.0. The next run is Monday.
What
Drop the local manager rather than port it. The shared preset's customManagers entry already covers catalog component pins in .gitlab-ci.yml, and does it better: it resolves through the gitlab-releases datasource with a hardcoded packageName instead of gitlab-tags, which is the lookup currently failing across eight other projects in the group.
That leaves this project at the convergence target for the estate — a bare extends of the shared preset with nothing local.
Also repoints extends from the //presets/renovate.json shim to the canonical :renovate-config named preset.
The one pin here, component: gitlab.com/gitlab-com/public-sector/pipeline/pages@v4.1.2, stays tracked: the preset's regex manager matches it.
Validation
renovate-config-validator --strict against renovate 43.272.0 passes.
Related
Pairs with pipeline!83 (merged), which fixes the schedule-window bug that has kept the whole group from opening MRs since May.