Upgrade MUI 5 TO 6#1129
Merged
Merged
Conversation
LarsKemmann
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR upgrades the project from MUI v5 to MUI v6 while also preparing the codebase for smoother future MUI migrations. The main goal was to make the upgrade process stable, safe, and production-ready without changing the current UI or runtime behavior. A big part of the work involved stabilizing the MUI dependency ecosystem, removing existing migration blockers, and reducing the risk of future major upgrades. This also helps position the application for easier transitions to future versions like MUI v7, v8, and v9. React remains on version 18.3.1 as part of this PR to keep the migration scope controlled and predictable.