Issues in monorepo with 2 different major versions of same package

[Whelch]

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.

Github, renovate version 39.136.0

Please tell us more about your question or problem

I have a monorepo library repository in which 2 distinct packages list the same dependency (eslint), but at different major versions - one is on version 8 while the other is on version 9. We have renovate configured to make distinct PRs for non-major version changes (patch & minor), and a separate PR for major version changes.

In our case, it seems like renovate is detecting a minor version bump for one of our package.json files (the one already on version 9), and incorrectly declaring the other update as a minor version bump as well
The renovate PR has the changes listed like this:

Package	Type	Update	Change
eslint (source)	dependencies	minor	^8.57.1 -> ^9.19.0
eslint (source)	dependencies	minor	^9.18.0 -> ^9.19.0

This is also happening for dependencies that aren't even being updated in both packages. For instance, eslint-plugin-react-hooks is only being updated in the lower-version package.json, and despite being hoisted up a whole major version, it's being declared as a patch in the renovate table

Package	Type	Update	Change
eslint-plugin-react-hooks (source)	dependencies	patch	^4.6.2 -> ^5.1.0

Is there some way this sort of miss-attribution of what's a major vs minor version update can be configured, in our case, in a general sense? I'm aware I could target eslint directly, by adding a couple of packageRules like this:

  "packageRules": [
    {
      "matchPaths": ["packages/my-package-1"],
      "matchPackageNames": ["eslint"],
      "allowedVersions": "^8.0.0"
    },
    {
      "matchPaths": ["packages/my-package-1"],
      "matchPackageNames": ["eslint-plugin-react-hooks"],
      "allowedVersions": "^4.0.0"
    }
  ]

However, I would like to be able to ensure this doesn't happen for any packages in the future.

Logs (if relevant)

Logs

2025-01-27 00:50:36.459 | DEBUG: Updating eslint-plugin-react-hooks in packages/my-package-1/package.json (repository=MyOrg/my-monorepo, branch=renovate/all)
2025-01-27 00:50:36.459 | DEBUG: npm.updateDependency(): dependencies.eslint-plugin-react-hooks = ^5.1.0 (repository=MyOrg/my-monorepo, branch=renovate/all)
2025-01-27 00:50:36.442 | DEBUG: Updating eslint in packages/my-package-2/package.json (repository=MyOrg/my-monorepo, branch=renovate/all)
2025-01-27 00:50:36.442 | DEBUG: npm.updateDependency(): dependencies.eslint = ^9.19.0 (repository=MyOrg/my-monorepo, branch=renovate/all)
2025-01-27 00:50:36.426 | DEBUG: Updating eslint in packages/my-package-1/package.json (repository=MyOrg/my-monorepo, branch=renovate/all)
2025-01-27 00:50:36.426 | DEBUG: npm.updateDependency(): dependencies.eslint = ^9.19.0 (repository=MyOrg/my-monorepo, branch=renovate/all)

[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