explaingit

home-operations/renovate-presets

★ 15JSON5Audience · ops devopsComplexity · 2/5ActiveSetup · easy

TLDR

Shareable Renovate config presets focused on the Kubernetes and homelab ecosystem, providing custom managers, overrides, and versioning rules but no opinionated grouping or scheduling.

Mindmap

mindmap
  root((renovate-presets))
    Inputs
      Existing renovate json
      Kubernetes or homelab repo
    Outputs
      Extra dependency detection
      Corrected package metadata
      Custom version schemes
    Use Cases
      Track CloudNativePG versions
      Detect Talos Factory image versions
      Fix source and changelog URLs
    Tech Stack
      Renovate
      JSON5
      Kubernetes

Things people build with this

USE CASE 1

Pull in all home-operations Renovate presets with one extends line

USE CASE 2

Add a single managers preset to detect dependencies in a custom file pattern

USE CASE 3

Override the source or changelog URL for a misconfigured upstream package

USE CASE 4

Apply a custom versioning scheme for projects that do not use semver tags

Tech stack

RenovateJSON5Kubernetes

Getting it running

Difficulty · easy Time to first run · 30min

Drop-in for an existing Renovate setup, so the only gotcha is choosing between the broad default extends and a more selective file-path reference.

In plain English

This repository is a collection of shareable configuration files for Renovate, a popular automation bot that watches a code repository and opens pull requests when the third-party software it depends on has new versions available. Renovate already knows how to track many common package types out of the box, but in larger setups it sometimes misses dependencies that are referenced in unusual ways. The home-operations group has gathered the workarounds it uses across its own projects and published them here so that other people can pull them into their own Renovate configuration with one line. The focus is on the Kubernetes and homelab ecosystem, including projects such as CloudNativePG, which runs PostgreSQL inside Kubernetes, and Talos Factory, which builds custom images for the Talos Linux distribution. The README emphasises that the repository ships only managers, package overrides, and a small amount of commit message policy. It deliberately does not ship opinionated rules for grouping pull requests, scheduling, or auto-merging, on the basis that those choices belong to the user's own repository. Usage is straightforward. A consumer adds an extends line to their renovate.json file pointing at github>home-operations/renovate-presets, which loads default.json and brings in every preset in this repo. A more selective consumer can reference a single file by path, for example a specific managers file ending in .json5, and they can pin to a tag or commit by appending #1.0.0 to the reference. The README also explains the directory layout. The config folder holds top-level Renovate settings such as registry aliases and file-pattern extensions. The managers folder holds custom regex and datasource managers. The overrides folder corrects metadata like the source URL or change-log URL for specific packages. The policies folder holds opt-in commit message rules. The versioning folder defines custom version schemes for upstream projects that publish tags which are not standard semantic versions. Each preset file documents its own purpose and any caveats inline.

Copy-paste prompts

Prompt 1
Add github>home-operations/renovate-presets to my renovate json and explain what changes
Prompt 2
Pick the right preset for tracking CloudNativePG image versions in my Kubernetes repo
Prompt 3
Pin my extends line to a specific tag like 1.0.0 and explain the trade-off
Prompt 4
Walk me through writing a new managers file in the same style for my own tool
Prompt 5
Explain why this repo deliberately leaves out grouping and auto-merge rules
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.