Disable Renovate; the repo is no longer maintained

[spaceninja]

Overview

Pleasantest is no longer actively maintained, so this turns Renovate off here rather than migrating it onto the shared preset the other 22 Cloud Four repos now use (cloudfour/renovate-config#1).

The practical argument is that Renovate had already stopped doing anything useful. The old config set prConcurrentLimit: 3, and three Renovate PRs have sat open since 2024 (#789, #791, #792) — so Renovate has been unable to open a new PR since March 2025. The elaborate rule set was inert, just noisily so.

Migrating instead of disabling would have made things worse, not better: clearing the concurrency deadlock would restart the PR flow, and the shared preset auto-merges patch and minor updates. That means a stream of auto-merged commits on a repo nobody is releasing from. Dependency updates only reach users through a publish, and the last one was v5.0.0 in July 2024.

Security coverage is unaffected — Dependabot still reports advisories, which is the part that matters for an unmaintained public package.

The reasoning lives in a description field in the config itself, along with the one-line extends needed to re-enable maintenance, so whoever looks at this next doesn't have to find this PR.

Screenshots

Testing

• Open .renovaterc.json on this branch and read the description — it should explain why Renovate is off and how to turn it back on
• After merging, confirm no new Renovate PRs appear on this repo
• Confirm the Dependency Dashboard issue stops updating (an existing dashboard issue may remain; it just goes stale)
• Confirm the repo's Security tab still lists Dependabot alerts — those are independent of Renovate and should be unchanged

---

Closes the last open item in cloudfour/renovate-config#1