Update @mui/material 5.0.0-rc.1 → 5.14.14 (minor) #240
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.14) · 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 47 commits:
[system] Bump package version (#39485)v5.14.14 (#39475)[styled-engine-sc] Fix TS issues because of missing types (#39395)[material][tab] Show/hide scroll buttons for dynamically added children (#39415)Bump @babel/traverse from 7.23.0 to 7.23.2 (#39479)Bump @babel/traverse to ^7.23.0 [SECURITY] (#39478)[website] Add the LinkedIn profile to the contributors section on the About page (#39455)[website] Update new role template (#39386)[material-ui][Table] Bug in "Sorting & Selecting" demo (#39426)Bump vitest to ^0.34.6 (#39451)Bump @vitejs/plugin-react to ^4.1.0 (#39452)Bump react-redux to ^8.1.3 (#39446)Bump react-virtuoso to ^4.6.2 (#39447)Bump rollup to ^3.29.4 (#39448)Bump vite to v4.4.11 (#39450)[docs] Accessibility in Base UI (#39264)[website] Add stray design fine-tunning to the Pricing page (#39472)[Divider][material-next] Add Divider component (#39179)[docs] Fix 301 redirection[docs-infra] Add refinements to the API content design (#39425)[icons] Fix VoiceChatOutlined showing the wrong icon (#39418)[mui-system][style] bug fix for style value check color in nullable object (#39457)[docs][base-ui] Renaming demos to BaseXxx (#39104)Bump @rollup/plugin-replace to ^5.0.4 (#39435)Bump @googleapis/sheets to ^5.0.5 (#39434)[docs][joy-ui] Fix row hover prop name in the Table page (#39431)[docs] Improve Base UI table of contents for APIs (#39412)[core] Fix multiple typos across the repo (#39422)[docs] Adjust design kits-related content (#39367)[docs-infra] Add a min height to the layout component (#39416)[docs-infra] Prevent horizontal scroll in the TOC (#39417)[docs][joy-ui] Fix color inversion demos (#39403)[docs] Revise the Contributing Guide (#39190)[joy-ui][typography] Update docs after lineHeight changes (#39366)[docs-infra] Add a collapsible list & table views to the API content display (#38265)[base-ui][Menu] Do not reopen the menu after clicking on a trigger in Safari (#39393)[material-ui][Box] Fix system properties has incorrect `Theme` interface when applied directly (#39404)[docs-infra] Adjust the `kbd` tag styles (#39397)[docs][material-ui] Remove irrelevant TODO from Snackbar demo (#39396)[joy-ui][Skeleton] Fix semi-transparent scenario when with surface components and color inversion (#39400)[material-ui][AvatarGroup] Add `renderSurplus` prop (#39283)[material-ui][Pagination] Update `type` parameter of `getItemAriaLabel` prop (#39390)[material-ui][AppBar] Support all default palette colors in TypeScript (#39389)[joy-ui][Textarea] Fix focus ring for error state (#39391)[joy-ui][List] Add the `marker` prop (#39313)[docs-infra] Fix strong style regression (#39384)[website] Fix career anchor link to perks & benefits👉 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