Update @mui/material: 5.0.0-rc.1 → 5.11.4 (minor) #184
Conversation
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
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.4) · 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 27 commits:
5.11.4 (#35771)[core] Fix the product license reference name (#35703)[Autocomplete] Add index to renderOption's AutocompleteRenderOptionState (#35578)[Tabs] Throw error only if individual `Tab` is hidden, not the whole `Tabs` (#34026)Bump MUI X to 6.0.0-alpha.14 (#35425)[docs] Revise and expand Joy UI Button doc (#35737)[Tooltip] Remove `data-foo` attribute (#35736)Bump sinon to ^15.0.1 (#35621)[Select] Revert "Update `renderValue` prop's TypeScript type (#34177)" (#35733)[examples] Add `Vite.js with TypeScript` example (#35683)[Joy] Miscellaneous improvements (#35769)[core] Close 2022 developer survey[core] Use TypeScript AST instead of TTP for component doc building (#35379)[docs] Document the workaround for crashing a translated page (#35720)[Portal][base] Convert code to TypeScript (#35657)Bump GitHub Actions (major) (#35613)[Autocomplete] Fix grammar in console.error in `useAutocomplete` (#35723)[Modal] Fix can't override Backdrop Props using new Slots API (#35140)Bump nx to ^15.4.4 (#35615)[Joy] Improve `onKeyDown` event handler for demo (#35642)[Autocomplete][joy] Specify `type` attribute for popup indicator (#35648)[docs] Fix API page for `MenuItem` to list all valid props (#35561)[TextField] Improve WCAG 2.4.7 with error={true} (#35687)[docs] Fix ad exception in Joy UI (#35685)[docs] Fix content wider than screen regression[website] Improve Lead Designer role description (#35684)[test] Always use & for nesting styles (#35702)👉 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