fix(deps): replace dependency @material-ui/icons with @mui/icons-material 5.0.0 - - package.json

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@material-ui/icons (source) → @mui/icons-material	dependencies	replacement	4.11.3 → 5.0.0

⚠️ Renovate's replacement functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

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

---

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 is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @finos/git-proxy@2.0.0-rc.4
npm error Found: react@16.14.0
npm error node_modules/react
npm error   react@"^16.14.0" from the root project
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     peerOptional @emotion/react@"^11.5.0" from @mui/material@5.18.0
npm error     node_modules/@mui/material
npm error       peer @mui/material@"^5.0.0-rc.0" from @mui/icons-material@5.0.0
npm error       node_modules/@mui/icons-material
npm error         @mui/icons-material@"5.0.0" from the root project
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.18.0
npm error       node_modules/@mui/material
npm error         peer @mui/material@"^5.0.0-rc.0" from @mui/icons-material@5.0.0
npm error         node_modules/@mui/icons-material
npm error   1 more (@emotion/styled)
npm error
npm error Could not resolve dependency:
npm error peer react@"^17.0.0 || ^18.0.0 || ^19.0.0" from @mui/material@5.18.0
npm error node_modules/@mui/material
npm error   peer @mui/material@"^5.0.0-rc.0" from @mui/icons-material@5.0.0
npm error   node_modules/@mui/icons-material
npm error     @mui/icons-material@"5.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-03T10_31_10_264Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-03T10_31_10_264Z-debug-0.log

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	7f0b8fc
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/69a6b87519c8cb0008d815d2

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/@mui/icons-material	5.0.0	🟢 7.8	Details Check Score Reason Code-Review 🟢 9 Found 20/22 approved changesets -- score normalized to 9 Packaging ⚠️ -1 packaging workflow not detected Dependency-Update-Tool 🟢 10 update tool detected Maintained 🟢 10 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege CII-Best-Practices 🟢 5 badge detected: Passing License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 10 all dependencies are pinned Branch-Protection 🟢 4 branch protection is not maximal on development and all release branches Fuzzing ⚠️ 0 project is not fuzzed SAST 🟢 7 SAST tool detected but not run on all commits Vulnerabilities ⚠️ 0 17 existing vulnerabilities detected CI-Tests 🟢 10 29 out of 29 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 35 contributing companies or organizations

Scanned Files

• package.json

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (5.0.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[jescalada]

Closing to reduce clutter (update emails, open PRs). We already have an issue to track MUI removal #1106 and a MUI upgrade/replacement in the works as of #1397