chore(renovate): restore the Renovate configuration

[CybotTM]

Renovate is not running on this repository, and the reason is a file that went missing rather than a decision.

This repository was onboarded in February 2025: #100 "Configure Renovate" merged renovate.json into main on 2025-02-19, and roughly a hundred Renovate pull requests followed over the next month. They stop in March 2025.

The file is not in the tree today, and no commit touching renovate.json exists anywhere in the current history — not on main, not on v4, not on any ref; the merge commit for #100 is gone as well. So main was rewritten after that merge and the configuration went with it, silently. Renovate then treats the repository as not onboarded and skips it, which is exactly when the pull requests stopped.

The content is the canonical form used by the other 127 repositories in the organization — a single extends of github>netresearch/renovate-config, which is where the policy lives (stability days, the automerge rules, the deps-no-automerge label). The 2025 onboarding config predates that preset, so this is not a byte-for-byte restore.

Dependabot stays for now. Removing it is a separate step per repository, taken once Renovate is demonstrably running here, not on the strength of this file existing.

Verified with Renovate's own validator, not just JSON syntax: INFO: Config validated successfully.

Assisted by claude-code:claude-opus-5 — Session

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 61a69a98-c112-4bfd-bdca-9429b06a3768

📥 Commits

Reviewing files that changed from the base of the PR and between 9a39213 and d3a31ad.

📒 Files selected for processing (1)

• renovate.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds a renovate.json file. The file declares the Renovate JSON schema and extends the shared github>netresearch/renovate-config preset.

Merge Risk: ⚪ Minimal · up to d3a31

This restores the repository’s Renovate configuration and shared update policies without introducing a material merge-readiness risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description clearly explains that the pull request restores the missing Renovate configuration, describes the shared preset, and documents validation and scope.
Title check	✅ Passed	The title clearly and concisely identifies the main change: restoring the Renovate configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/add-renovate-config

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch chore/add-renovate-config

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[CybotTM]

Self-review: d3a31ad

The review this pull request demands is unsatisfiable (Copilot quota wall or repeated bot failures on this head). Per the documented fallback, the diff on this head was reviewed by the PR author; this comment is the on-the-record attestation the merge gate reads back. It stops matching on the next push.