fix: Add validations for aliases

[adusumillipraveen]

Currently aliases for helm-requirements is failing when configured during nested json validation.

INFO: Repository has invalid config
{
  "error": {
    "configFile": ".github/renovate.json",
    "validationError": "The renovate configuration file contains some invalid settings",
    "validationMessage": "Invalid configuration option: helm-requirements.aliases.stable"
  }

Closes https://github.com/renovatebot/config-help/issues/679

[adusumillipraveen]

@rarkins any thoughts on this PR ? I am not sure if this is the right fix, but happy to contribute if you can guide me.

[rarkins]

@adusumillipraveen we don't actually do the validation you're seeing using a JSON validator - it's an internal tool with a bit more config awareness. So unfortunately I think the solution is instead to add aliases awareness to https://github.com/renovatebot/renovate/blob/master/lib/config/validation.ts

We should check:

• aliases is an object
• The object is one deep
• values of each field are valid URIs

[adusumillipraveen]

@adusumillipraveen we don't actually do the validation you're seeing using a JSON validator - it's an internal tool with a bit more config awareness. So unfortunately I think the solution is instead to add aliases awareness to https://github.com/renovatebot/renovate/blob/master/lib/config/validation.ts

We should check:

• aliases is an object
• The object is one deep
• values of each field are valid URIs

Thanks @rarkins , i pushed a commit to add specific validations for aliases along with some tests. Please review.

[rarkins]

Please check if we can reuse the existing is module for url validation

[renovate-release]

🎉 This PR is included in version 20.25.7 🎉

The release is available on:

• GitHub release
• 20.25.7

Your semantic-release bot 📦🚀