[core] Do not let Renovate handle examples packages updates

[ZeeshanTamboli]

• I have followed (at least) the PR section of the contributing guide.

I noticed renovate opening dependency updates PR for the examples packages to a major version. We eventually close them because we don't want the legacy example material-next-ts-v4-v5-migration, which uses @mui/styles for styling to use the latest versions of Next.js and React (See multiple closed PRs for examples (major)). All examples packages are pinned to the latest versions except material-next-ts-v4-v5-migration.

I propose to altogether remove the config from renovate. Those who are not aware of it could unknowingly merge them.

[mui-bot]

Netlify deploy preview

https://deploy-preview-37386--material-ui.netlify.app/

Bundle size report

No bundle size changes

Generated by 🚫 dangerJS against 62fc883

[mnajdova]

Should we be more explicit and define:

    {
      "groupName": "examples",
      "matchPaths": ["examples/**/package.json"],
      "enabled": false
    },

Is this equivalent? I haven't tried if this config exist. Is there way to validate if this works somehow?

[ZeeshanTamboli]

Should we be more explicit and define:

    {
      "groupName": "examples",
      "matchPaths": ["examples/**/package.json"],
      "enabled": false
    },

Is this equivalent? I haven't tried if this config exist. Is there way to validate if this works somehow?

It's not equivalent. You are correct. We need to be explicit to disable updates by setting enabled: false. Otherwise, it will still open PRs. The default is true. This should work because another example is of node which was done in #30659.

[mnajdova]

Great, thanks @ZeeshanTamboli for being proactive to add change this config :)