Extend shared Renovate preset

[spaceninja]

Overview

cloudfour/renovate-config is now the shared Renovate preset source for Cloud Four repos. This repo was still on the deprecated config:base and had none of the settings the other 22 repos share, so moving it onto the preset is a real behavior change, not a rename. It's landing on its own so the change is easy to see and easy to revert.

Before:

{ "extends": ["config:base"] }

What changes:

• config:base → config:recommended. config:base is deprecated; config:recommended is its supported successor.
• Patch and minor updates will now auto-merge. This repo had no auto-merge at all, so this is the largest change here — dependency PRs that pass CI will land without you touching them. Majors still always require review.
• Exact versions will be pinned instead of left as ranges.
• Updates wait three days after release before a PR opens, so a package that ships a broken version and pulls it has time to do so before we see it.

This repo isn't published to npm, so it uses the default preset rather than library.

Note the config stays in renovate.json — most repos use .renovaterc.json, but Renovate treats the two identically and renaming would add churn for no functional gain.

Screenshots

Testing

• Open renovate.json on this branch — it should contain only a $schema line and a single extends entry pointing at local>cloudfour/renovate-config
• After merging, open the Dependency Dashboard issue and wait for Renovate to run (or tick the checkbox at the bottom of the dashboard to request an immediate run)
• The dashboard should render its usual list of pending updates with no error banner at the top. A red "Config Validation" or "Preset Not Found" warning would mean the preset failed to resolve
• Given auto-merge is new here, watch the first patch or minor PR and confirm you're comfortable with it merging on its own once CI passes
• Confirm new dependency PRs pin an exact version rather than a range like ^1.2.3

---

Part of cloudfour/renovate-config#1