Update @mui/material 5.0.0-rc.1 → 5.14.17 (minor) #245
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.14.17) · 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 34 commits:
5.4.17 (#39773)[lab] Remove tree view import from `@mui/lab` (#39685)[docs] Update Taiwan country name in demos (#39729)[test] Fix flaky screenshot (#39711)[material-ui][Dialog] Should not close until the IME is cancelled (#39713)[website] List benefits for sponsors (#39640)[core][docs] Fix broken MUI System link in README.md (#39734)[joy-ui][ModalDialog] Remove redundant code (#39719)[docs][joy-ui] Make code readable to set next color in color inversion demos (#39669)[material-next][OutlinedInput] Copy v5 OutlinedInput (#39698)[joy-ui][ToggleButtonGroup] Fix toggling button state when `Button` is not immediate children (#39571)[docs-infra] Fix path bloat client-side (#39708)[docs-infra] Render footer in SSR (#39710)[docs-infra] Simplify footer (#39709)[InputBase][material-next] InputBase slotProps accepts sx type (#39714)[docs-infra] Fix dark theme color (#39720)[docs-infra] Remove the design feedback alert (#39691)[zero][system] Support props from "as" component (#39611)[website] Add Vadym teamMember card to 'About' (#39701)[docs–infra] Small polish on API toggle (#39704)[base-ui] Make list components more reliable (#39380)[material-ui][InputBase] Add `sx` type to `input` , `root` slot (#39569)[docs][material-ui] Remove numeric input workaround from TextField docs (#39629)[docs-infra] Bring back scroll gradient in API page with table (#39689)[docs-infra] Clarify the content of the ads[docs-infra] Link to ScaffoldHub v2Bump Playwright (#39131)[docs-infra] Improve access to the component demos via the API page (#39690)[docs-infra] Add appropriate aria-label to docs buttons (#39638)[core] Speed up the CI by removing the second build (#39684)[docs][material-ui] Add comment about code to be removed from Drawer demo (#39678)Bump MUI X (#39659)[docs] Update release doc for unchanged packages (#39487)[docs-infra] Fix crawler on API pages (#39490)👉 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:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `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