Update @mui/icons-material 5.0.0-rc.1 → 5.16.8 (minor) #309
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.16.8) · 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 33 commits:
v5.16.8 (#44550)[core] Cherry pick React 19 added to peer dependencies to v5.x (#44578)[typescript] Cherry pick React 19 type PRs to v5.x (#44577)[core] Bump pnpm to 9.14.2 in v5.x branch (#44574)[material-ui][Autocomplete] Cherry-pick #43189 (#44561)[test] Cherry-pick React 19-related test PRs (#44557)[utils] skip deep clone React element (v5.x) (#44494)[material-ui] Cherry pick ref accessing PRs (#44543)[core] Cherry pick #42346 to v5 (#44475)[core] Fix CI on v5.x branch (#44487)[examples] Fix v5 clone example instructions (#43755)[docs] Keep sponsors up to date[docs] Fix MUI Treasury Layout broken links (#43753)[docs] Strengthen CSP rule[docs] Give up on restoring search[docs] Normalize next major message[docs] Fix versions URL[docs] Fix use of absolute URLs (#43567)[examples] Fix CLI download instructions[examples] Fix CDN live preview example[examples] Fix more examples to work with v5[examples] Freeze examples dependency range (#43435)[docs] Restore search on v5 (#43566)[core] Fix CI on v5.x branch (#43564)[docs] fix link from v5 to v6 (#43585)[website] Fix link redirection[blog] Polish Upcoming changes to MUI X pricing in 2024 (#43438)[docs] Updated mui-x roadmap links with the new project URL (@michelengelen) (#43446)Prepare for moving to v5.x branch (#43447)[blog] Add video to the Pigment CSS blog post (#42500)[website] Add buzzoid and twicsy as gold sponsors (@rluzists1) (#43397)[docs] Fix broken link to Next.js docs[blog] Announcing pricing changes Sep 2024 (#43272)👉 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