gitmyhub

renovate-presets

JSON5 ★ 20 updated 18h ago

Community project for shared Renovate configuration

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

RenovateJSON5Kubernetessetup: easycomplexity 2/5

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.

Where it fits