Update @mui/material: 5.0.0-rc.1 → 5.11.10 (minor) #192
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @mui/material (5.0.0-rc.1 → 5.11.10) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 23 commits:
Prepare release 5.11.10 (#36268)[Joy] Add `zIndex` to theme (#36236)[docs] Fix 301 links[docs] Fix modal transition demos (#36137)[docs] Update links to pt examples (#36237)[useMediaQuery] Fix behavior of noSsr with React 18 (#36056)[Avatar] Fix ownerState usage with styleOverrides when fallback is used (#36228)[docs][base] Fix base Input demos for Safari (#36213)[docs] Update custom Typography variants example (#36185)[core] Migrate nprogress to emotion (#36181)[core] Enforce namespace import for ReactDOM (#36208)[TextareaAutosize] Convert code to TypeScript (#35862)[Badge][material] Replace `BadgeUnstyled` with `useBadge` hook (#36158)[Switch] Fix DOM warning when `type` isn't `checkbox` or `radio` (#36170)[docs] Change markdown numbering syntax (#36187)[Joy] Remove transition from all components (#35952)[docs] Fix switch alignment in `Disabled tree items` section in Tree View docs (#36217)[docs][joy] Update class name prefixes in the `Anatomy` section (#36210)[docs] Standardize example names (#36112)[docs] Fix typo[docs] Fix markdown table alignments (#36136)[core] Fix deploy preview links (#36203)[docs] Small color tweaks to the docs search bar (#36160)👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands