-
Notifications
You must be signed in to change notification settings - Fork 5
chore: upgrade MUI to v9.1.0 #163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
rchalamala
merged 2 commits into
devin/1781145070-lazy-term-catalogs
from
devin/1781144786-mui-9-upgrade
Jun 11, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 MUI v7→v9 is a major version jump skipping v8
The PR bumps
@mui/icons-materialand@mui/materialfrom^7.3.11directly to^9.1.0, skipping major version 8 entirely. While TypeScript compilation passes and all current imports resolve correctly, skipping a major version means two sets of breaking changes and migration guides apply. There may be subtle runtime behavioral changes (e.g., default prop values, styling/theming changes, accessibility attributes) that wouldn't surface at compile time. Worth verifying visually that components likeCollapse,Switch,IconButton, andDialogrender and behave as expected.Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified visually: ran the app on both MUI 7 (main) and MUI 9 (this branch) side by side and exercised
Dialog(help + More Info),Collapse,Switch, and allIconButtons through the UI — identical rendering and behavior, no console errors. Note MUI Core has no v8 release on npm (versions go 7.3.11 → 9.0.0-alpha.0), so only the single v7→v9 migration guide applies; the only relevant breaking change was the removedHelpOutlineicon alias, handled in this PR. Full evidence in the test results comment.