Add renovate configuration for mintmaker

[joselsegura]

Description

Add renovate configuration for mintmaker

Type of change

• Configuration update

Testing steps

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0b571f5d-e465-41ab-b94d-80d18f1a78cd

📥 Commits

Reviewing files that changed from the base of the PR and between 319e3d6 and 3f713c9.

📒 Files selected for processing (1)

• .github/workflows/renovate-config-check.yaml

---

Summary by CodeRabbit

• Chores
  • Configured Renovate to automatically merge grouped dependency updates for pre-commit, PyPI (Python), Go modules, and GitHub Actions, treating major/minor updates together.
  • Added an automated validation workflow to check the Renovate configuration on pushes and pull requests to ensure the config remains valid.

Walkthrough

Adds a new renovate.json configuring automerge/grouping rules for several package sources and a GitHub Actions workflow .github/workflows/renovate-config-check.yaml that validates renovate.json on push and pull_request events.

Changes

Cohort / File(s)	Summary
Renovate configuration renovate.json	New file adding four packageRules that set automerge: true, platformAutomerge: true, and grouping metadata (groupName, groupSlug, separateMajorMinor: false) for PyPI (matchDatasources: ["pypi"]), pre-commit (matchManagers: ["pre-commit"]), Go modules (matchManagers: ["gomod"]), and GitHub Actions (matchManagers: ["github-actions"]).
Renovate config validation workflow .github/workflows/renovate-config-check.yaml	New GitHub Actions workflow "Validate renovate.json config file" that runs on push (main/master) and pull_request, checks out the repo and runs konflux-ci/renovate-config-validator-action@main with config_file: renovate.json.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the primary change: adding a renovate configuration file for the mintmaker project.
Description check	✅ Passed	The description is related to the changeset, clearly stating that it adds renovate configuration and categorizing it as a configuration update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

🧹 Nitpick comments (2)

renovate.json (2)

3-8: Consider limiting automerge to non-major updates.

The current rule will automerge all pre-commit updates, including major version bumps that might introduce breaking changes. While pre-commit hooks are typically lower-risk than application dependencies, you may want to restrict automerging to minor and patch updates for additional safety.

🛡️ Optional enhancement to limit automerge scope

 {
   "description": "Automerge pre-commit config updates",
   "matchManagers": ["pre-commit"],
+  "matchUpdateTypes": ["minor", "patch"],
   "automerge": true,
   "platformAutomerge": true
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@renovate.json` around lines 3 - 8, The current Renovate rule sets "automerge"
and "platformAutomerge" to true for "matchManagers": ["pre-commit"], which
permits major version bumps to be merged automatically; change the automerge
configuration so only non-major updates are auto-merged (e.g., replace the
boolean "automerge" and/or "platformAutomerge" with a structured automerge
policy that explicitly restricts allowedUpdateTypes to ["minor","patch"] or
otherwise disable platformAutomerge for pre-commit to prevent major updates from
being automerged.

---

1-10: Consider extending from a base Renovate preset.

The configuration lacks an extends field, meaning Renovate will use minimal defaults. Most projects extend from standard presets like ["config:recommended"] to get sensible default behavior for dependency updates, PR creation, scheduling, and more.

📋 Suggested enhancement to add base configuration

 {
+  "extends": ["config:recommended"],
   "packageRules": [
     {
       "description": "Automerge pre-commit config updates",
       "matchManagers": ["pre-commit"],
       "automerge": true,
       "platformAutomerge": true
     }
   ]
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@renovate.json` around lines 1 - 10, Add a base preset to the Renovate config
by adding an "extends" array that includes a recommended preset (e.g.,
"config:recommended") at the top level of the JSON so Renovate uses sensible
defaults; update the existing object that contains "packageRules" (the block
with "matchManagers": ["pre-commit"] and "automerge": true) to coexist with the
new "extends" key rather than replacing defaults.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@renovate.json`:
- Around line 3-8: The current Renovate rule sets "automerge" and
"platformAutomerge" to true for "matchManagers": ["pre-commit"], which permits
major version bumps to be merged automatically; change the automerge
configuration so only non-major updates are auto-merged (e.g., replace the
boolean "automerge" and/or "platformAutomerge" with a structured automerge
policy that explicitly restricts allowedUpdateTypes to ["minor","patch"] or
otherwise disable platformAutomerge for pre-commit to prevent major updates from
being automerged.
- Around line 1-10: Add a base preset to the Renovate config by adding an
"extends" array that includes a recommended preset (e.g., "config:recommended")
at the top level of the JSON so Renovate uses sensible defaults; update the
existing object that contains "packageRules" (the block with "matchManagers":
["pre-commit"] and "automerge": true) to coexist with the new "extends" key
rather than replacing defaults.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 15693749-dc4f-44c1-91c2-2c08e1c304a0

📥 Commits

Reviewing files that changed from the base of the PR and between d2b424e and 77911e8.

📒 Files selected for processing (1)

• renovate.json