Update @mui/icons-material 5.0.0-rc.1 → 5.15.14 (minor) #278
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/icons-material (5.0.0-rc.1 → 5.15.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 43 commits:
[release] v5.15.14 (#41540)Bump @types/node to ^18.19.25 (#41518)[material-next] Drop the package (#41544)[docs-infra] Make the Algolia search input label invisible (#41542)[material-ui][docs] Fix landing page template's h1 size (#41543)[material-ui][docs] Apply new code header docs feature (#41508)[website] Improve navbar's items hover state (#41535)fix lint vale issue[docs] Fix useStorageState regressions (#41223)Bump github/codeql-action action to v3.24.7 (#41521)Bump eslint-plugin-react to ^7.34.1 (#41520)Bump MUI X (#41519)Bump @argos-ci/core to ^1.5.5 (#41517)Bump react-virtuoso to ^4.7.2 (#41527)Bump react-intersection-observer to ^9.8.1 (#41526)Bump google-auth-library to ^9.7.0 (#41525)Bump aws-sdk to ^2.1579.0 (#41524)Bump @types/lodash to ^4.17.0 (#41523)Bump markdown-to-jsx to ^7.4.3 (#41522)[pigment-css][docs] Add media query guide (#41473)[material-ui] Use interface instead of type for props (#41500)[docs-infra] Fail CI on Vale error (#40944)[core] Use Circle CI context (#41532)[docs-infra] Improve Vale config[docs] Fix some Vale errors (#41516)[blog] Bringing consistency to Material UI customization APIs (#41040)[docs-infra] Add a feature list "component" (#41484)[docs-infra] Add code block header classes (#41487)[pigment-css][nextjs-plugin] Follow-up to #41494 (#41502)[code-infra] Rename @mui-internal/docs-utils to @mui/internal-docs-utils (#41498)[docs][pigment-css] Fixing location of the ExtendTheme type in the docs (#41499)[pigment-css] Add Box component (#41451)[website] Split Toolpad documentation (#41316)[pigment-css][nextjs-plugin] Fix alias resolver (#41494)[material-ui][Select] Fix variant type (#41405)[material-ui][Progress] Add Circular progress gradient demo from Github comment (#40559)[website] Use MUI X Data Grid v7-beta (#41276)[core] Fix CHANGELOG format and update date (#41481)[Accordion] Convert to support CSS extraction (#41221)[Autocomplete] Convert to support CSS extraction (#40330)[joy-ui][docs] Add UI improvements to the side navigation demo (#41461)[code-infra] Copy translations.json to @mui/docs build folder (#41472)[Slider][material-ui] Make it zero-runtime compatible (#41201)👉 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