Registry alias name change (#33922) no longer groups images from the same place together

[JamesMHenderson]

How are you running Renovate?

Self-hosted Renovate

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

GitLab, renovate v39.146.1

Please tell us more about your question or problem

The recent change to the way aliases were handled (#33922) stops renovate automatically grouping dependencies if they are from the same place but have different alias names.

We have the example where we have a CI variable to reference a harbor cache ($CI_REGISTRY_IMAGE) in our gitlab-ci file which in our CI pipelines are configured to point to our harbor cache

e.g

  services:
    - name: $CI_REGISTRY_CACHE/selenium/standalone-firefox:120.0@sha256:a405fe92b3ce5d7eb31a07e1f99be3d628fdc0e5bdc81febd8dc11786edef024
      alias: selenium

Renovate is then configured to alias this to to docker.io

We then have a docker-compose file that we run locally so do not have the variable CI_REGISTRY_CACHE configured so need to reference docker.io directy

version: '3.8'
services:
  chrome:
    image: 'docker.io/selenium/standalone-chrome:121.0@sha256:529a9b0ab0e41bf1bc9a8984c4b803e30160042d3bec9a8454d65afd6db023ee'
    container_name: chrome-selenium

Before the change in #33922 as the images were the same these were grouped as they are updating the same docker image, but not renovate separates them out to treat them as separate dependencies. Is it possible to revert this breaking change of behaviour in config so that aliases are treated as they were previously without configuring custom package rules?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[viceice]

this is an expected side effect. you need to manually group them if you want.

this is now the same behavior as with not automatically grouping alpine and docker.io/library/alpine.