chore(deps): use shared Renovate config

[Coldaine]

User description

Summary

• Add a minimal Renovate config that extends the shared MooseGooseConsulting preset.
• Use the no-dashboard, low-concurrency, agent-review dependency policy from MooseGooseConsulting/renovate-config.
• Leave existing Dependabot config in place for this first rollout pass unless Renovate is already confirmed active for the repo.

Shared config: https://github.com/MooseGooseConsulting/renovate-config

Validation

• Shared preset validated with renovate-config-validator --strict in MooseGooseConsulting/renovate-config.
• This repo config is the same minimal extends shape validated in MooseGooseWebsite.

Renovate Configuration Introduction

Changes Made

A new renovate.json configuration file has been added to establish Renovate as a dependency management tool for this repository.

File Structure

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "github>MooseGooseConsulting/renovate-config"
  ]
}

Configuration Approach

Aspect	Details
Strategy	Minimal configuration that extends a shared preset
Base Config	MooseGooseConsulting/renovate-config (GitHub)
Policy	No-dashboard, low-concurrency, agent-review dependency policy
Overrides	None—all policies inherited from shared preset
Validation	Preset validated using renovate-config-validator --strict

Additional Notes

• Dependabot Configuration: Retained in place during this initial Renovate rollout phase pending confirmation of active deployment
• Pattern Match: Configuration structure matches the previously validated setup from MooseGooseWebsite repository
• Review Label: Marked for agent review

Summary

Metric	Value
Lines Changed	+6 / -0
Files Modified	1
Review Effort	Low
Breaking Changes	None

---

CodeAnt-AI Description

Use the shared Renovate settings for dependency updates

What Changed

• Added a Renovate config that points this repo at the shared MooseGooseConsulting dependency-update setup
• Keeps dependency update behavior aligned with the team’s standard review and scheduling rules

Impact

✅ Consistent dependency update handling
✅ Fewer setup differences across repositories
✅ Easier maintenance of update settings

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7d46d717-b736-4bbd-89b7-827ce43325a7

📥 Commits

Reviewing files that changed from the base of the PR and between 8db783a and 8507ae6.

📒 Files selected for processing (1)

• renovate.json

---

📝 Walkthrough

Walkthrough

A renovate.json file is added to the repository root. It declares the Renovate JSON schema URL and extends a shared preset from MooseGooseConsulting/renovate-config on GitHub, with no additional overrides.

Changes

Renovate Dependency Update Configuration

Layer / File(s)	Summary
Renovate config file renovate.json	Creates the Renovate configuration file with a schema reference and a single preset extension pointing to MooseGooseConsulting/renovate-config.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops in, config in paw,
"Renovate shall keep deps without flaw!"
One JSON file, so small and neat,
A shared preset makes updates sweet.
🐇✨ No more stale locks — what a treat!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: introducing a shared Renovate configuration. It is concise, specific, and clearly conveys the primary purpose of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/use-shared-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 and usage tips.}

[Copilot]

Pull request overview

This PR introduces a Renovate configuration for the repository by adding a minimal renovate.json that delegates policy to the shared MooseGooseConsulting/renovate-config preset, aligning dependency automation behavior with the org standard.

Changes:

• Add renovate.json with schema reference and a single extends entry to the shared MooseGooseConsulting preset.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• renovate.json - No issues

---

Documentation observation (not blocking): The repo lacks an AGENTS.md file to serve as a central workflow router and entry point for documentation. While not related to this PR's scope, consider adding one to reference the key docs (NORTH_STAR.md, AGENT_STANDUP_PROMPT.md, NOTES.md) for clarity.

---

_{Reviewed by deepseek-v4-flash-20260423 · Input: 38.6K · Output: 4.4K · Cached: 156.4K}

[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