registryAliases looks not applied by the helm-values manager

[cridam]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

Other (please specify)

Which version of Renovate are you using?

43.256.0

Please tell us more about your question or problem

My original goal is to interfere with the loopupName suggested by the helm-values by translating myrepo.io/folder/xxx => myrepo.io/staging-folder/xxx

I try to use registryAliases in that scope.

Description

registryAliases appears to be ignored when Docker image dependencies are extracted from a Helm values.yaml file using the helm-values manager.

The same configuration does not produce any lookup change for dependencies managed by helm-values.

Environment

• Renovate version: 43.256.0
• Manager: helm-values
• Datasource: docker

Minimal reproduction

values.yaml

image:
  registry: docker.io
  repository: nginx
  tag: 1.27

renovate.json

{
  "packageRules": [
    {
      "matchManagers": [
        "helm-values"
      ],
      "registryAliases": {
        "docker.io": "registry.example.com"
      }
    }
  ]
}

Expected behavior

Renovate should apply the registry alias when resolving the Docker dependency.

The dependency should still be updated in values.yaml as:

image:
  registry: docker.io
  repository: nginx
  tag: <new-version>

but the Docker datasource lookup should use:

registry.example.com/nginx

instead of:

docker.io/nginx

Actual behavior

The alias is not applied.

The extracted dependency remains:

{
  "depName": "docker.io/nginx",
  "packageName": "docker.io/nginx",
  "lookupName": "nginx",
  "registryUrl": "https://docker.io"
}

No lookup is performed against registry.example.com.

Additional information

The same registryAliases configuration appears to be ignored for dependencies extracted by the helm-values manager.

Could you please clarify whether registryAliases is expected to be supported by helm-values?

If supported, this looks like a bug where the alias is not propagated from the manager extraction phase to the Docker datasource lookup phase.

Logs (if relevant)

"deps": [
{
"depName": "docker.io/library/nginx",
"packageName": "docker.io/library/nginx",
"currentValue": "1.27",
"datasource": "docker",
"replaceString": "1.27",
"versioning": "docker",
"autoReplaceStringTemplate": "{{newValue}}{{#if newDigest}}@{{newDigest}}{{/if}}",
"updates": [
{
"bucket": "non-major",
"newVersion": "1.31",
"newValue": "1.31",
"releaseTimestamp": "2026-06-25T01:51:08.300Z",
"newVersionAgeInDays": 13,
"newMajor": 1,
"newMinor": 31,
"newPatch": null,
"updateType": "minor",
"isBreaking": false,
"libYears": 1.038241788559107,
"branchName": "renovate/charts"
}
],
"warnings": [],
"registryUrl": "https://index.docker.io",
"lookupName": "library/nginx",
"currentVersion": "1.27",
"currentVersionTimestamp": "2025-06-11T02:51:15.256Z",
"currentVersionAgeInDays": 392,
"isSingleVersion": true,
"fixedVersion": "1.27"
}

[RahulGautamSingh]

registryAliases doesn't take effect inside packageRules

Registry aliases are applied during the extract phase. But packageRules are only evaluated later, during the per-dependency lookup phase. So a registryAliases object nested inside a packageRules entry never reaches the extractor, and the alias is silently ignored.

Set it either at the top level (applies to all managers) or scoped to a specific manager by its name:

{
  "helm-values": {
    "registryAliases": {
      "docker.io": "registry.example.com"
    }
  }
}

The docs show these two forms.

[cridam]

Thanks a lot , it works !