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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@material-ui/styles (source) → @mui/styles	dependencies	replacement	^4.10.0 → ^5.0.0
@material-ui/styles (source) → @mui/styles	dependencies	replacement	^4.11.0 → ^5.0.0
@material-ui/styles (source) → @mui/styles	dependencies	replacement	^4.9.6 → ^5.0.0

This is a special PR that replaces @material-ui/styles 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]

EntelligenceAI PR Summary

This PR replaces the deprecated @material-ui/styles (MUI v4) dependency with @mui/styles (MUI v5) across five Backstage plugins and updates the lockfile accordingly.

• Affected plugins: code-coverage, cost-insights, sonarqube, techdocs, techdocs-react
• Version constraint updated from ^4.11.0 to ^5.0.0 in all plugin package.json files
• yarn.lock upgraded @babel/runtime from 7.21.0 to 7.29.2, removing regenerator-runtime as an explicit dependency
• @mui/utils, @mui/private-theming, and @mui/types bumped to latest 5.x versions
• Added material-table@1.69.3 and its full dependency tree (jspdf, canvg, html2canvas, react-beautiful-dnd, etc.)
• plugin-gitops-profiles workspace @backstage/* packages (core-plugin-api, core-components, config, theme) pinned to older npm versions (0.1.x) instead of workspace-local references
• Legacy versions of markdown/remark/micromark/unified packages added to satisfy pinned @backstage/core-components@0.1.0 and react-markdown@^5.0.2 dependencies

---

Confidence Score: 3/5 - Review Recommended

Likely safe but review recommended — this PR performs a straightforward package rename from @material-ui/styles to @mui/styles across five Backstage plugins (code-coverage, cost-insights, sonarqube, techdocs, techdocs-react), which is a well-understood MUI v4→v5 migration step. However, the @mui/styles package in MUI v5 is itself a compatibility/legacy package that relies on JSS and is not recommended for new work, so merging this may lock the codebase into a deprecated styling approach rather than advancing toward the MUI v5-idiomatic @mui/material styled/sx API. The yarn.lock changes — notably upgrading @babel/runtime from 7.21.0 to 7.29.2 and dropping regenerator-runtime as an explicit dependency — should be validated to ensure no transitive breakage occurs across the broader monorepo.

Key Findings:

• The @mui/styles package is explicitly marked as legacy in MUI v5 and still depends on JSS; this migration moves off a deprecated v4 package but lands on another deprecated v5 compatibility shim, meaning the technical debt is not resolved and could require another migration pass soon.
• The yarn.lock bump of @babel/runtime from 7.21.0 to 7.29.2 and removal of regenerator-runtime as an explicit transitive dependency is a non-trivial lockfile change in a monorepo; without CI evidence or test coverage across all five affected plugins, there is latent risk of runtime breakage in async/generator-heavy code paths.
• No review comments or automated findings were raised against the changed package.json files in the five plugins, and the rename itself is mechanically correct — the package name change from @material-ui/styles to @mui/styles with an updated semver range ^5.0.0 is the standard migration path.
• Coverage of the changed files was 0/6 in automated review, meaning the lockfile and all five package.json files were not deeply inspected for peer-dependency conflicts (e.g., @mui/styles v5 requires @mui/material v5 peer dep, which should be confirmed present in each affected plugin).

Files requiring special attention

• yarn.lock
• plugins/cost-insights/package.json
• plugins/techdocs/package.json
• plugins/techdocs-react/package.json

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates several Backstage plugin packages to replace the direct dependency on @material-ui/styles with @mui/styles.

Changes:

• Updated plugins/code-coverage to depend on @mui/styles@^5.0.0 instead of @material-ui/styles
• Updated plugins/cost-insights to depend on @mui/styles@^5.0.0 instead of @material-ui/styles
• Updated plugins/sonarqube to depend on @mui/styles@^5.0.0 instead of @material-ui/styles
• Updated plugins/techdocs to depend on @mui/styles@^5.0.0 instead of @material-ui/styles
• Updated plugins/techdocs-react to depend on @mui/styles@^5.0.0 instead of @material-ui/styles
• Refreshed yarn.lock to reflect the dependency replacement

Technical Notes: This appears to be an automated Renovate replacement intended to move from the v4 package name to the MUI v5 legacy styles package while keeping the rest of the Material UI v4 stack in place.

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

[augmentcode]

Review completed. 2 suggestions posted.

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

[augmentcode]

This package still imports from @material-ui/styles (e.g. plugins/techdocs-react/src/component.tsx), so replacing the declared dependency here may cause repo/package dependency checks to fail (or end up relying on transitive deps). Other locations where this applies: plugins/code-coverage/package.json:36, plugins/sonarqube/package.json:47, plugins/techdocs/package.json:51.

Severity: high

Other Locations

• plugins/code-coverage/package.json:36
• plugins/sonarqube/package.json:47
• plugins/techdocs/package.json:51

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

[augmentcode]

@mui/styles@5.0.0 has a react peer dependency of ^17.0.2, but these plugins advertise compatibility with react ^16.13.1 || ^17.0.0, which can create peer-dependency conflicts for React 16 (and even 17.0.0/17.0.1) consumers. Other locations where this applies: plugins/code-coverage/package.json:36, plugins/cost-insights/package.json:45, plugins/sonarqube/package.json:47, plugins/techdocs/package.json:51.

Severity: medium

Other Locations

• plugins/code-coverage/package.json:36
• plugins/cost-insights/package.json:45
• plugins/sonarqube/package.json:47
• plugins/techdocs/package.json:51

_{🤖 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
	@​azure/​identity@​3.2.3
	@​esbuild-kit/​cjs-loader@​2.4.2
	@​gitbeaker/​browser@​35.8.1
	@​gitbeaker/​node@​35.8.1
	@​material-ui/​core@​4.12.4
	@​material-ui/​lab@​4.0.0-alpha.61
	@​material-ui/​pickers@​3.3.10
	@​date-io/​core@​1.3.13
	@​kubernetes-models/​base@​4.0.3
	@​aws-sdk/​util-arn-parser@​3.310.0
	@​aws-sdk/​abort-controller@​3.370.0
	@​graphql-codegen/​typescript-resolvers@​3.2.0
	@​graphql-codegen/​graphql-modules-preset@​3.1.2
	@​graphql-codegen/​typescript@​3.0.3
	@​date-io/​luxon@​1.3.13
	@​frsource/​cypress-plugin-visual-regression-diff@​3.3.10
	@​aws-sdk/​middleware-endpoint@​3.370.0
	@​aws-sdk/​util-stream-node@​3.370.0
	@​aws-sdk/​types@​3.370.0
	@​graphql-tools/​schema@​9.0.19
	@​aws-sdk/​node-http-handler@​3.370.0
	@​aws-sdk/​signature-v4@​3.370.0
	@​graphql-codegen/​cli@​3.3.0
	@​manypkg/​get-packages@​1.1.3
	@​kubernetes-models/​apimachinery@​1.2.1
	@​mui/​styles@​5.18.0
	@​keyv/​memcache@​1.3.7
	@​codemirror/​language@​6.8.0
	@​microsoft/​api-documenter@​7.19.27
	@​jest-mock/​express@​2.0.2
See 44 more rows in the dashboard

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 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: ? → npm/@microsoft/api-extractor@7.33.7 → npm/typescript@4.8.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.8.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