Michael Kriese

I think this should also only be possible for config files. so we don't need the bad import from config to worker in PR.

I think we don't need to change anything for cli and env vars, they should be validated as is now. So those extra values can only be occure in config...

> I'm wondering if this should instead be a RENOVATE_X_SKIP_CONFIG_VALIDATION option because its use should be very rare agreed 👍

yes, but only in changelogs.

maybe also needs `customChangelogsDirectory`

those should then passt to all functions in changelogs, so they are evaluated once, like platform detection

you shouldn't set `engines.yarn=*` without setting `packageManager` field to a V1 yarn. otherwise renovate will use latest yarn version from npm, which is a V2 release. checkout versions on npmjs

yes, for constraints we don't follow tags on npmjs, we just use highest matching version, which is of cause a 2.x

looks like a config issue to me, as the url is totally wrong. the registry url is duplicated.

reproduction isn't public