Renovate unexpectedly opens multiple Gitlab MRs for group of Rust dependencies

[jonhoo]

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, 38.27.0

Please tell us more about your question or problem

In an internal project on a self-hosted Gitlab, I have renovate configured to group together changes to a number of related dependencies. All the dependencies are Cargo dependencies, they are all in the same (custom) registry, and their names all start with foobar-. I have configured them to be grouped with a rule like:

    {
      groupName: 'foobar changes',
      matchPackageNames: ['/^foobar-/'],
    },

My project is now in a state where there's been a new version of all the foobar- crates (specifically, 0.69.0 -> 0.70.1). However, unexpectedly, Gitlab created a new MR for each foobar- crate, each one with a branch name like renovate/foobar-subcratename-0.x.

Now, when I run renovate locally with --platform=local (and --allow-custom-crate-registries to allow the custom registry), I see that all the updates in the packageFiles with updates (repository=local) debug log entry are listed with "branchName": "renovate/foobar-changes" as expected. The same is the case whether I run the latest renovate code from main or a checkout of the version our infrastructure is running.

Any ideas as to how this discrepancy may have arisen?

Logs (if relevant)

Sadly I don't have access to the renovate logs from the Gitlab infrastructure. I could try to get them if it helps narrow down the problem, but it is non-trivial to do so.

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Insufficient logs

Select me to read instructions

If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team

[rarkins]

Unfortunately, we'd need debug logs to be able to work out what's going on