Inherited config should be resolved before merging

[rarkins]

Describe the proposed change(s).

Discussion: #31182

To address this:

• We should resolve presets in inherited config prior to merging the config in
• We should log a debug message saying we're doing this
• We should document this behavior clearly, including noting that it's not possible to use an ignorePresets entry to ignore a preset in the extends of inherited config

[RahulGautamSingh]

We should document this behavior clearly, including noting that it's not possible to use an ignorePresets entry to ignore a preset in the extends of inherited config

We can still ignore the presets in inherited config if the ignorePresets is enabled from file config. Do you want to never ignore presets in inherited config?

[rarkins]

I meant it's not possible to ignore it from repo config. It's ok to ignore it from global (although I'm not sure that's likely)

[viceice]

so this no longer works?

https://github.com/visualon/renovate-config/blob/febda028480f14509fada8e327da6dea1d468a70/shared.json#L24

I'm using ignore presets inside my shared preset. 🤔

[RahulGautamSingh]

Unless you have these shared presetes inside inherited config, they should work.

[rarkins]

@viceice is that an inherited config? or an explicitly extended preset?

[viceice]

@viceice is that an inherited config? or an explicitly extended preset?

explicit extended

[rarkins]

I don't think this change would affect that

[renovate-release]

🎉 This issue has been resolved in version 39.63.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.63.1

Your semantic-release bot 📦🚀