Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update material-ui monorepo to v5.15.5 - autoclosed #145

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 17, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@mui/icons-material (source) 5.15.4 -> 5.15.5 age adoption passing confidence
@mui/material (source) 5.15.4 -> 5.15.5 age adoption passing confidence

Release Notes

mui/material-ui (@​mui/icons-material)

v5.15.5

Compare Source

Jan 17, 2024

A big thanks to the 18 contributors who made this release possible. Here are some highlights ✨:

  • Base UI's CSS class prefix is now base- (#​40205) @​michaldudak
  • Bug fixes, and a lot of improvements to code and docs infra
@mui/material@5.15.5
@mui/material-next@6.0.0-alpha.118
@mui/base@5.0.0-beta.32
Breaking changes

The class prefix of Base UI components have been changed from Mui- to base-. This only affects codebases that uses class names verbatim, i.e. not exposed by JS objects such as buttonClasses, but as plain strings or in CSS stylesheets (.MuiButton.root)

To adapt your code to the new pattern:

  • replace all occurrences of the regex .Mui([A-Z][A-Za-z]*)- with .base-$1- (so MuiButton-root becomes base-Button-root, etc.),
  • replace all occurrences of the regex .Mui-([a-z]*) with .base--$1 (so Mui-disabled becomes base--disabled, etc.).
Changes
@mui/joy@5.0.0-beta.23
@mui/codemod@5.15.5
@mui/lab@5.0.0-alpha.161
@mui/material-nextjs@5.15.5
@mui/system@5.15.5
Docs
Core

All contributors of this release in alphabetical order: @​2metres, @​aacevski, @​brijeshb42, @​danilo-leal, @​DiegoAndai, @​josh-feldman, @​Kamino0, @​lhilgert9, @​maakcode, @​michaldudak, @​oliviertassinari, @​petrovmiroslav, @​sai6855, @​samuelsycamore, @​siriwatknp, @​zanivan, @​ZeeshanTamboli, @​zinoroman


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

changeset-bot bot commented Jan 17, 2024

⚠️ No Changeset found

Latest commit: 6b069d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title fix(deps): update dependency @mui/material to v5.15.5 fix(deps): update material-ui monorepo to v5.15.5 Jan 17, 2024
@renovate renovate bot force-pushed the renovate/material-ui-monorepo branch from 49c8a4e to 6b069d3 Compare January 17, 2024 18:14
@renovate renovate bot changed the title fix(deps): update material-ui monorepo to v5.15.5 fix(deps): update material-ui monorepo to v5.15.5 - autoclosed Jan 22, 2024
@renovate renovate bot closed this Jan 22, 2024
@renovate renovate bot deleted the renovate/material-ui-monorepo branch January 22, 2024 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants