[core] Move @mui/internal-test-utils to dev dependency

[LukasTy]

Fixes #13317.

• Move the @mui/internal-test-utils dependency from dependencies to devDependencies on the @mui/x-data-grid package.
• Change version to a stable released package 1.0.0.

WDYT @mui/code-infra, wouldn't it be more correct if the internal package stable versions were released with the latest flag instead of next? 🤔

[mui-bot]

Deploy preview: https://deploy-preview-13318--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 0c3f0d1

[cherniavskii]

Thanks for fixing this!

[DysektAI]

Possible to get this merged?
I actually updated about an hour ago and got quite the warning output which was odd. I'm sure this is worthy of a small patch.

Output:

[Janpot]

I think the plan is to have internal packages always on canary versions in dependent repositories. I'm under the assumption the intention is:

latest: 1.0.0 - published while public packages are published. We don't use this verison in X/Toolpad/base
canary: 1.0.0-dev.20240529-082515-213b5e33ab - published with every change on master. We use this version in X/Toolpad/base. But we specify the exact evrsion number so that renovatebot can automate the upgrade

So, I think the 1.0.0-dev.20240529-082515-213b5e33ab version was as intended. The npm tags seem wrong to me

cc @michaldudak

[LukasTy]

latest: 1.0.0 - published while public packages are published. We don't use this verison in X/Toolpad/base
canary: 1.0.0-dev.20240529-082515-213b5e33ab - published with every change on master. We use this version in X/Toolpad/base. But we specify the exact evrsion number so that renovatebot can automate the upgrade

Ok, gotcha, if that's the intent, we can adjust the approach. 👌
And I think that the tags are correct in such a case because renovate would only suggest bumping a package to a newer latest release, if we'd release all the master pushes as next, then renovate wouldn't prompt for an upgrade.
Am I missing something?

[Janpot]

I suppose we can configure renovatebot to follow a specific tag, but since this is an internal package we can probably leave it as is