Package rule identification from the match string patterns for the same dependency

[mvgadagi]

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.

No response

Please tell us more about your question or problem

I have a scenario where the same package is used in two different keys within a build.yaml file, and I want Renovate to handle updates for each key separately.
Here’s the current configuration in the build.yaml:

buildImage: 'dockerhub.test.net/ci-build-image/build-image:1.35.33'
buildBetaImage: 'dockerhub.test.net/ci-build-image/build-image:1.35.33'

We are extracting dependencies like this using Renovate's regexManagers:

"regexManagers": [
  {
    "fileMatch": ["build.yaml$"],
    "matchStrings": ["buildImage: 'dockerhub.test.net/ci-build-image/(?<depName>.*?):(?<currentValue>.*?)'"],
    "datasourceTemplate": "docker",
    "registryUrlTemplate": "https://dockerhub.test.net/ci-build-image"
  },
  {
    "fileMatch": ["build.yaml$"],
    "matchStrings": ["buildBetaImage: 'dockerhub.test.net/ci-build-image/(?<depName>.*?):(?<currentValue>.*?)'"],
    "datasourceTemplate": "docker",
    "registryUrlTemplate": "https://dockerhub.test.net/ci-build-image"
  }
]

While we discovered that we can use additionalBranchPrefix, we’re unable to distinguish between buildImage and buildBetaImage in the packageRules because they share the same registry, package name, and datasource.
This limitation comes because we are not allowed to use matchStrings inside packageRuels

Is there a way to configure Renovate to treat buildImage and buildBetaImage differently and apply separate update configurations for each one?

Why we need this:
• We want separate PRs for buildImage and buildBetaImage.
• We need the flexibility to configure different update strategies (e.g., minor, major, patch) for each.

Any advice or suggestions would be greatly appreciated!

Logs (if relevant)

Logs

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

[rarkins]

Distinguish then using depName

[mvgadagi]

Actually I have tried the packageRules as this with latest renovate version with config and I see some warning in the logs, could you please check if I am making any mistakes in the configuration.

Thanks a lot for you response !!

  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "includeForks": true,
  "regexManagers": [
    {
      "fileMatch": [
        "build.yaml$"
      ],
      "matchStrings": [
        "buildImage: 'dockerhub.test.net/ci-build-image/(?<depName>.*?):(?<currentValue>.*?)'"
      ],
      "datasourceTemplate": "docker",
      "depName": "buildImage",
      "registryUrlTemplate": "https://dockerhub.test.net/ci-build-image"
    },
    {
      "fileMatch": [
        "build.yaml$"
      ],
      "matchStrings": [
        "buildBetaImage: 'dockerhub.test.net/ci-build-image/(?<depName>.*?):(?<currentValue>.*?)'"
      ],
      "datasourceTemplate": "docker",
      "depName": "buildBetaImage",
      "registryUrlTemplate": "https://dockerhub.test.net/ci-build-image"
    }
  ],
  "packageRules": [
    {
      "matchDatasources": [
        "docker"
      ],
      "groupName": "buildImage",
      "depName": "buildImage"
    },
    {
      "matchDatasources": [
        "docker"
      ],
      "groupName": "buildBetaImage",
      "depName": "buildBetaImage"
    }
  ]
}```


then in the logs I see these errors

WARN: Config validation errors found in renovate.json
"errors": [
{
"topic": "Configuration Error",
"message": "Custom Manager contains disallowed fields: depName"
},
{
"topic": "Configuration Error",
"message": "Custom Manager contains disallowed fields: depName"
},
{
"topic": "Configuration Error",
"message": "Invalid configuration option: customManagers[0].depName"
},
{
"topic": "Configuration Error",
"message": "Invalid configuration option: customManagers[1].depName"
},
{
"topic": "Configuration Error",
"message": "Invalid configuration option: packageRules[1].depName"
},
{
"topic": "Configuration Error",
"message": "Invalid configuration option: packageRules[2].depName"
}
]

DEBUG: depName mismatch (repository=TEST/renovate-sample, packageFile=build.yaml, branch=renovate/buildbetaimage)
"manager": "regex",
"currentDepName": "buildBetaImage",
"newDepName": "build-image"

[rarkins]

You need to use depNameTemplate in the custom manager, not depName.

[rarkins]

And please look up the docs for packageRules, you will see that depName is not a valid option and should not need to ask here

[mvgadagi]

Thank you for the response, sorry I was not sure when you mentioned to Distinguish then using depName hence tried adding depName in packageRules,
so becaue of this constraint I believe this scenario is not possible for the moment..

[rarkins]

It's actually possible, if you use depNameTemplate in custom managers and matchDepNames in packageRules