Does configMigration work for updating presets?

[gaeljw]

Tell us more.

I just found out that Renovate is able to work on its own config files but would it be able to open PR/MRs for presets? I tried the option and it didn't do anything.

Here's the setup I'm thinking of:

• project renovate-common-config: with a default.json containing a bunch of configs + a renovate.json (referencing itself)
• projects that contains a renovate.json that references the preset "extends": ["local>renovate-common-config"]

When Renovate runs on the renovate-common-config, it doesn't seem to do anything. I definitely have some legacy configurations that I know should be upgraded. I guess it only looks at the renovate.json file but not at the default.json file.

[rarkins]

It doesn't migrate presets yet, contributions for this would be welcome

[gaeljw]

I'd be happy to give it a try if someone can give some hints.

I guess this wouldn't be implemented as a manager/data source but rather something else ad-hoc?

I need to read the code to find where upgrade to renovate.json files are managed first :)

[rarkins]

The challenge is that presets can have any file name in a repo. Renovate can't just check every file in every repo in case they contain presets.

So this would require:

• Renovate to be running on the preset repo in the first place, and
• Some type of config which lets you tell Renovate file names or patterns to check

Perhaps the easiest way would be to do this via a renovate.json in the same repo, and a new config option like presetValidations which accepts glob patterns. e.g. to validate every json file except the renovate.json it could be ["*.json", "!renovate.json"]