matchRegistryUrls requires all registries to match, even if they don't all apply to the specific MR

[andrewducker]

How are you running Renovate?

Self-hosted Renovate CLI

Which platform you running Renovate on?

GitLab (.com or self-hosted)

Which version of Renovate are you using?

43.104.7

Please tell us more about your question or problem

We have two registry urls we use for nuget:

{
     matchDatasources: ['nuget'],
      registryUrls: [
        'https://artifactory.myco.com/artifactory/api/nuget/myco-ngt-release',
        'https://artifactory.myco.com/artifactory/api/nuget/nuget-remote'
     ]
}

The first is for our internal packages. The second is a cache for external packages.

We want to do different things depending on whether an MR is for internal packages or external packages.

However, after a lot of testing, it looks like matchRegistryUrls only activates if all of the registry urls for a given package type are matched.

I demonstrated this with:

    {
      matchRegistryUrls: ["/https:\/\/artifactory\.myco\.com\/artifactory\/api\/nuget\/[mn].........../"],
      prBodyNotes: ["A Match!"],
    },

This only matches if the regex contains both an m and and n as [mn]. (for "myco-ngt-release" and "nuget-remote")

Can you confirm that the matchRegistryUrls cannot tell which registries are used for a specific MR? Or am I being very confused?

[andrewducker]

Hi, your final sentence seems to have been truncated.

If I do want to have different text in my MR based on the registry it's pulling from, is there any way of doing that?

[roelarents]

1. It seems like all registry URLs are used as input(s). Not only the one where the package was found.
   https://github.com/renovatebot/renovate/blob/43.226.1/lib/util/package-rules/registryurls.ts#L20

2. But then only some of those need to match.
   https://github.com/renovatebot/renovate/blob/43.226.1/lib/util/string-match.ts#L66