renovatebot/renovate

Support for dynamic repository configuration

Open

#21110 opened on Mar 23, 2023

View on GitHub
 (10 comments) (4 reactions) (0 assignees)TypeScript (14,066 stars) (1,916 forks)batch import
core:confighelp wantedpriority-4-low

Description

What would you like Renovate to be able to do?

I would like to configure renovate in my repository using a dynamically-created repository config.

Use case

In my repository, we have branches for every minor version that we publish. e.g. 14.2.x, 14.3.x, 15.0.x. In a simplified manner, we would like Renovate to only operate on the two most highest SemVer branches. This is currently not possible to achieve via a RegExp.

There are ways to achieve it by manually disabling Renovate for these older branches, but we would like to avoid manually having to maintaining this list/landing changes in older branches.

We have a script that will tell us the most recent branches that are "still in active development" and would like to use it to configure Renovate. Also with a dynamic configuration, we can have different configurations for different semantic branches. e.g.

- main   // should use active @next version of Angular
- 15.2.x // should active @latest version of Angular
- 15.1.x // no longer in active development. Would not like Renovate PRs
- 15.0.x // no longer in active development. Would not like Renovate PRs

If you have any ideas on how this should be implemented, please tell us here.

Mostly thinking of supporting a .js, .mjs, .cjs config file in a repository. Renovate would then run it via Node. It would be opt-in only for self-hosted users. The configuration file could not depend on any node_modules?

Is this a feature you are interested in implementing yourself?

Maybe

Contributor guide

Tech stack
typescriptjavascriptnodejs
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Renovate's configuration systemNode.js module loadingJavaScript/TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the current configuration loading mechanism in the Renovate codebase, particularly how config files are parsed and merged (see lib/config/). Review the linked discussion (#20867) for additional context and potential design decisions. Consider implementing a module loader that evaluates .js/.mjs/.cjs config files using Node.js, ensuring it is opt in for self hosted users and does not depend on node modules. Look at existing config file formats (JSON, JSON5, YAML) to understand the integration points.