How to separate MUI and MUI-X updates?

[khitrenovich]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

42.85.1

Please tell us more about your question or problem

Recently we finally managed to push Material UI v6 => v7 upgrade through the finish line. This took us quite some time, mostly due to the breaking changes. Once it was done, we found out that MUI-X upgrades were stuck behind, accumulating quite a gap (7.29.1 => 8.25.0).

MUI-X packages have the same @mui scope, but come from different repository (mui/mui-x) and have different version cadence - for example, MUI-X is now on v8.x and is compatible with MUI v5, v6 and v7 majors.

Currently we don't have any MUI-specific overrides in our Renovate configuration.

We would like to avoid such situation in the future, but I cannot think of an easy way to decouple those via Renovate config. Any help will be greatly appreciated.

Logs (if relevant)

Logs

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

[secustor]

AFAIK all MUI-X packages are prefixed with @mui/x-*.

So do you have tried to use that in a matcher matchPackageNames: [ "@mui/x-*" ]?

[khitrenovich]

Hm. I'm trying to recall why I thought it will interfere with regular MUI packages... but I see no reason why would it, indeed. Oops.