Upgrade to MUI v6

[FranckLecuyer]

PR Summary

Upgrade to MUI v6 (but keeping the now deprecated Grid component)

Waiting for PR to be merged : gridsuite/commons-ui#924

[coderabbitai]

Warning

Rate limit exceeded

@FranckLecuyer has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 25 minutes and 17 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6abd6d36-accc-4aa3-840b-258ab5712085

📥 Commits

Reviewing files that changed from the base of the PR and between 912ed76 and d9736ee.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

📝 Walkthrough

Walkthrough

Package dependency references updated: @gridsuite/commons-ui switched from a published version to a local tarball path; @mui/icons-material, @mui/material upgraded from 5.x to 6.x; @mui/lab upgraded from 5.x alpha to 6.x beta. No code or exported API changes.

Changes

Cohort / File(s)	Summary
Dependency Version Updates package.json	Replaced @gridsuite/commons-ui pinned published version (0.189.0) with a local tarball (file:../commons-ui/gridsuite-commons-ui-0.204.0.tgz); upgraded @mui/icons-material and @mui/material from ^5.18.0 to ^6.5.0; upgraded @mui/lab from 5.0.0-alpha.175 to 6.0.1-beta.36. No other changes.

Suggested reviewers

• flomillot

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Upgrade to MUI v6' directly and accurately describes the main change in the pull request, which upgrades Material UI packages to version 6.
Description check	✅ Passed	The description is directly related to the changeset, explaining the MUI v6 upgrade and noting the dependency on an external PR, which provides meaningful context for reviewers.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 25 minutes and 17 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 19: Replace the local tarball reference for the `@gridsuite/commons-ui`
dependency ("file:../commons-ui/gridsuite-commons-ui-0.199.0.tgz") with the
published version string (e.g., "0.199.0") in package.json and remove any file:
entries for `@gridsuite/commons-ui` in package-lock.json, then run npm install to
regenerate package-lock.json so CI and fresh installs use the published package;
finally commit the updated package.json and the regenerated package-lock.json.
- Around line 21-23: The package.json declares unsupported MUI major versions
(`@mui/material` and `@mui/icons-material` at ^6.5.0 and `@mui/lab` at 6.0.1-beta.36);
update these dependencies to a supported major (e.g., bump `@mui/material` and
`@mui/icons-material` to the current supported major v9 range and choose a
compatible `@mui/lab` release), or revert/remove the v6 entries so this PR is
non-mergeable until a coordinated upgrade is completed; after changing the
versions, run the package manager to update lockfiles and run the test/build
suite to surface any breaking API changes (look for references to `@mui/material`,
`@mui/icons-material`, and `@mui/lab` in package.json and the codebase).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 43ea5579-afad-4918-aab2-5202af745242

📥 Commits

Reviewing files that changed from the base of the PR and between fc43361 and 22f5e2c.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

MUI Material-UI supported versions official documentation 2026

💡 Result:

As of April 2026, the most recent stable version of MUI Material-UI is v9.0.0, which is recommended for production use. Older released versions include v7.0.0 (March 2025), v6.0.0 (August 2024), v5.0.6, and earlier. MUI follows Semantic Versioning 2.0.0 (major.minor.patch). The official support policy provides full support for the current stable major version, with security updates and regression fixes for the immediate predecessor major version. Older versions receive no support. From the versions page (https://mui.com/versions/), v9 is marked with ✓ (stable/current). Release schedule shows majors roughly every 6-12 months. No explicit LTS, but limited maintenance on the prior major (likely v8 or v7 now). Check the official versions page (https://mui.com/versions/) and support page (https://mui.com/material-ui/getting-started/support/) for the latest status, as policies evolve with releases.

Citations:

• 1: https://mui.com/versions/
• 2: https://mui.com/material-ui/getting-started/support/
• 3: https://v5.mui.com/material-ui/getting-started/support

---

Avoid landing an unsupported MUI major on main.

As of April 2026, MUI's support policy provides full support only for the current stable major (v9) and security updates for the immediate predecessor. Version 6.x receives no support. The package.json specifies @mui/material: ^6.5.0 and @mui/icons-material: ^6.5.0, which are unsupported versions. Either upgrade to a supported major version or keep this as a non-mergeable transitional PR pending a follow-up upgrade before release.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 21 - 23, The package.json declares unsupported MUI
major versions (`@mui/material` and `@mui/icons-material` at ^6.5.0 and `@mui/lab` at
6.0.1-beta.36); update these dependencies to a supported major (e.g., bump
`@mui/material` and `@mui/icons-material` to the current supported major v9 range
and choose a compatible `@mui/lab` release), or revert/remove the v6 entries so
this PR is non-mergeable until a coordinated upgrade is completed; after
changing the versions, run the package manager to update lockfiles and run the
test/build suite to surface any breaking API changes (look for references to
`@mui/material`, `@mui/icons-material`, and `@mui/lab` in package.json and the
codebase).

[antoinebhs]

weird that many changes in package lock?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud