webgrip/renovate-config

Fork 0

[PR #2] [MERGED] Compose GitOps Renovate preset from home-operations presets #12

New issue

Closed

opened 2026-06-08 09:05:03 +00:00 by ryangr0 · 0 comments

ryangr0 commented

2026-06-08 09:05:03 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/webgrip/renovate-config/pull/2
Author: @Copilot
Created: 6/1/2026
Status: ✅ Merged
Merged: 6/2/2026
Merged by: @Ryangr0

Base: main ← Head: copilot/use-renovate-config-from-repo

📝 Commits (3)

dd958bc Initial plan
b342152 Compose GitOps preset from home operations
7d1e2c5 Pin upstream home operations presets

📊 Changes

4 files changed (+129 additions, -273 deletions)

View changed files

📝 README.md (+2 -2)
📝 THIRD_PARTY_NOTICES.md (+2 -2)
📝 docs/renovate.md (+25 -5)
📝 gitops.json (+100 -264)

📄 Description

Summary

Make webgrip/renovate-config the shared homelab Renovate layer for webgrip/homelab-cluster: compose useful upstream home-operations/renovate-presets, then keep cluster-specific rules in the consuming repo.

Replaced locally duplicated GitOps manager/override config with selected, pinned upstream presets.
Kept Webgrip-specific Flux OCI digest handling, GitOps image digest policy, and PR labeling.
Documented the recommended homelab-cluster rollout:

{
  "extends": [
    "github>webgrip/renovate-config#v1.2.1",
    "github>webgrip/renovate-config:gitops#v1.2.1"
  ]
}

Presets affected

github>webgrip/renovate-config:gitops
- Extends selected home-operations/renovate-presets entries pinned to #1.3.1.
- Preserves Webgrip-only Flux OCIRepository and digest behavior.
Documentation and third-party notices updated for the new composition model.

Consumer impact

GitOps/homelab consumers get upstream home-operations extraction, overrides, semantic commit polish, and versioning without inheriting their full policy bundle.
Consumers should keep runtime and cluster-local rules in their own repo: credentials, hostRules, enabledManagers, allowedCommands, post-upgrade tasks, app/path-specific package rules, and maintenance windows.
Release impact: cut a new Webgrip tag before updating consumers; consumers should pin that tag.

Checklist

Documentation and examples are updated if behavior changed
The validator passes for every shared preset
The release/tagging impact is described

Original prompt

I want to use this repo's renovate config in my webgrip/homelab-cluster. That repo right now already has a renovate with a bunch of rules. I also want to use what I can from https://github.com/home-operations/renovate-presets. There are probably things in there that I could use / are already using in webgrip/renovate-config. I like good ideas and only want 10x solutions. My idea: webgrip/renovate-config has a config that extends from a bunch of home-operations/renovate-presets, and than the webgrip/renovate-config is extended in my webgrip/homelab-cluster, while keeping the cluster specific rules in there. Ideas? Plan it for me.

Created from VS Code.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/webgrip/renovate-config/pull/2 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 6/1/2026 **Status:** ✅ Merged **Merged:** 6/2/2026 **Merged by:** [@Ryangr0](https://github.com/Ryangr0) **Base:** `main` ← **Head:** `copilot/use-renovate-config-from-repo` --- ### 📝 Commits (3) - [`dd958bc`](https://github.com/webgrip/renovate-config/commit/dd958bc779ddc8b6d82573f8bfada5657e0051de) Initial plan - [`b342152`](https://github.com/webgrip/renovate-config/commit/b342152d8f4f3f91bf0a533f091b45f125b9ea52) Compose GitOps preset from home operations - [`7d1e2c5`](https://github.com/webgrip/renovate-config/commit/7d1e2c59ae11a8baf25ff5e0818e732ba747d0a2) Pin upstream home operations presets ### 📊 Changes **4 files changed** (+129 additions, -273 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+2 -2) 📝 `THIRD_PARTY_NOTICES.md` (+2 -2) 📝 `docs/renovate.md` (+25 -5) 📝 `gitops.json` (+100 -264) </details> ### 📄 Description ## Summary Make `webgrip/renovate-config` the shared homelab Renovate layer for `webgrip/homelab-cluster`: compose useful upstream `home-operations/renovate-presets`, then keep cluster-specific rules in the consuming repo. - Replaced locally duplicated GitOps manager/override config with selected, pinned upstream presets. - Kept Webgrip-specific Flux OCI digest handling, GitOps image digest policy, and PR labeling. - Documented the recommended homelab-cluster rollout: ```json { "extends": [ "github>webgrip/renovate-config#v1.2.1", "github>webgrip/renovate-config:gitops#v1.2.1" ] } ``` ## Presets affected - `github>webgrip/renovate-config:gitops` - Extends selected `home-operations/renovate-presets` entries pinned to `#1.3.1`. - Preserves Webgrip-only Flux `OCIRepository` and digest behavior. - Documentation and third-party notices updated for the new composition model. ## Consumer impact - GitOps/homelab consumers get upstream home-operations extraction, overrides, semantic commit polish, and versioning without inheriting their full policy bundle. - Consumers should keep runtime and cluster-local rules in their own repo: credentials, `hostRules`, `enabledManagers`, `allowedCommands`, post-upgrade tasks, app/path-specific package rules, and maintenance windows. - Release impact: cut a new Webgrip tag before updating consumers; consumers should pin that tag. ## Checklist - [x] Documentation and examples are updated if behavior changed - [x] The validator passes for every shared preset - [x] The release/tagging impact is described  <details> <summary>Original prompt</summary> > I want to use this repo's renovate config in my webgrip/homelab-cluster. That repo right now already has a renovate with a bunch of rules. I also want to use what I can from https://github.com/home-operations/renovate-presets. There are probably things in there that I could use / are already using in webgrip/renovate-config. I like good ideas and only want 10x solutions. My idea: webgrip/renovate-config has a config that extends from a bunch of home-operations/renovate-presets, and than the webgrip/renovate-config is extended in my webgrip/homelab-cluster, while keeping the cluster specific rules in there. Ideas? Plan it for me. </details>  Created from [VS Code](https://code.visualstudio.com/docs/copilot/copilot-coding-agent). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

ryangr0

2026-06-08 09:05:03 +00:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

webgrip/renovate-config#12

No description provided.

Rows
Columns