Replace dependency @material-ui/core with @mui/material ^5.0.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@material-ui/core (source) → @mui/material	dependencies	replacement	^4.12.2 → ^5.0.0
@material-ui/core (source) → @mui/material	dependencies	replacement	^4.9.13 → ^5.0.0
@material-ui/core (source) → @mui/material	dependencies	replacement	^4.12.4 → ^5.0.0
@material-ui/core (source) → @mui/material	peerDependencies	replacement	^4.12.2 → ^5.0.0

This is a special PR that replaces @material-ui/core with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: (UTC)

• 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 was generated by Mend Renovate. View the repository job log.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[entelligence-ai-pr-reviews]

Automatic Review Skipped

Too many files for automatic review.

If you would still like a review, you can trigger one manually by commenting:

@entelligence review

[augmentcode]

🤖 Augment PR Summary

Summary: This PR (Renovate-generated) replaces direct workspace dependencies on @material-ui/core with @mui/material (MUI v5) across many Backstage packages.

Changes:

• Updates numerous package.json files in packages/ and plugins/ to swap @material-ui/core → @mui/material at ^5.0.0.
• Adjusts packages/theme to peer-depend on @mui/material instead of @material-ui/core.
• Regenerates yarn.lock to reflect the dependency replacement and new transitive dependency graph.

Technical Notes: This is a major ecosystem switch (MUI v4 → v5) and may require corresponding updates to source imports, peer dependency alignment (e.g. Emotion), and compatibility checks with remaining MUI v4 packages (icons/lab/styles).

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 4 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

@mui/material is added here, but this workspace still has source imports from @material-ui/core (e.g. packages/app-defaults/src/defaults/components.tsx); with Yarn PnP this will likely break builds since @material-ui/core is no longer a declared dependency for the package.

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

This package still depends on @material-ui/icons / @material-ui/lab, which (at these v4 versions) typically declare a peer dependency on @material-ui/core; removing @material-ui/core in favor of @mui/material may leave unmet peers or incompatible expectations at runtime.

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

@mui/material (MUI v5) has required peers like @emotion/react and @emotion/styled; this package now depends on @mui/material but doesn’t list Emotion deps, which can surface as peer-dependency errors under Yarn PnP.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

The repo templates (e.g. packages/cli/templates/default-plugin/package.json.hbs) still reference @material-ui/core, so running yarn new may generate new packages that don’t match this PR’s dependency switch to @mui/material.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	react@​17.0.2
	typescript@​4.7.4
	swc-loader@​0.2.3
	storybook-dark-mode@​1.1.2
	react-hot-loader@​4.13.1
	react-dom@​17.0.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm polished under OFL-1.1 License: OFL-1.1 - The applicable license policy does not permit this license (5) (package/docs/assets/fonts/LICENSE.txt) From: ? → npm/@storybook/addon-actions@6.5.16 → npm/polished@4.2.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/polished@4.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm typescript under W3C-20150513 License: W3C-20150513 - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: LicenseRef-W3C-Community-Final-Specification-Agreement - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) From: storybook/package.json → npm/typescript@4.7.4 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.7.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!