disparate dependencies with the same name are improperly grouped

[dannysauer]

How are you running Renovate?

A Mend.io-hosted app

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 two "helm" dependencies in one repo. One is an asdf ".tool-versions" file, and the other is a Terraform provider. They do not depend upon one another even though both are technically running "the same" helm. As it turns out, they both had fairly recent updates. However, Renovate has grouped them together into one PR. I'm pretty sure this is not the desired behavior from anyone in this situation, particularly considering the helm binary update is a patch release while the Terraform provider update is a major release with breaking changes. :) Normally I want related changes bundled together, so I'd be hesitant to completely disable that feature. My renovate config is extremely simple:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:recommended",
    "helpers:pinGitHubActionDigests"
  ]
}

Is there a config option which says not to group dependencies with the same name from completely unrelated providers?

Here's a dark-mode picture to make my text look more exciting!

Logs (if relevant)

Logs

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

[github-actions[bot]]

Hi there,

Please help this Discussion progress 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