Is it possible to have renovate migrate my shared preset json file?

[wessel-terpstra-vf]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Azure DevOps

Please tell us more about your question or problem

I have a repostitory that contains a default.json with my renovate preset that is shared between different repositories on Azure DevOps. I have enabled the config migration setting and it migrates my renovate.json files successfully. However, it does not upgrade my default.json file that contains my shared preset.

Is it possible to point renovate to my default.json shared preset file to make sure it will migrate that too?

[HonkingGoose]

The configMigration docs does not say if a default.json shared preset file will get config migrated or not:

If enabled, Renovate raises a pull request when it needs to migrate the Renovate config file. Renovate only performs configMigration on .json and .json5 files.

We should definitely explain this better in the docs. I don't know the correct answer, so I'll let a maintainer answer. 😄

Renovate docs for configMigration config option

[rarkins]

Renovate does not discover/migrate presets yet, but we should create a feature request for it if none exists

[HonkingGoose]

These issues seem a bit related:

• Add feature to validate and migrate presets in same repo #22525
• Show user if config migration is needed for their own config or for an extends #21456
• Add globalPresets and repoPresets to global config, deprecate direct extends use #11791

[rarkins]

Yes #22525 is it

[wessel-terpstra-vf]

Thanks for clarifying! Keep up the epic work :)

[HonkingGoose]

I'll re-open this discussion so it's easy to find for others who have the same problem. Once we actually support migrating shared presets, we can close the discussion for real. 😄