@mui/utils
9.5.0 · 9 Oct 2026MIT21.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @mui/utils From 7.3.2 to 7.3.3
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 6
- fixes
Before you upgrade
Tick each one off as you go- Breaking7.3.3
Release by release
- Breaking
Remove
copy-filescommand usage from packages - Fixed
Fix year in Punta Cana retreat post
- Fixed
Fix github actions check for continuous release
- Fixed
Fix markdown generation script to find correct files
- Fixed
Fix unnecessary redirects
- Fixed
Fix JSON files not being imported in TS demos
- Fixed
Fix naming to match convention
- Breaking
24 other lines we could not sort, mostly version bumps
- 7.3.3
Punta Cana retreat post
- 7.3.3
Publish from CI
- 7.3.3
Convert reportBrokenLink script to ts
- 7.3.3
Update module resolution for typescript@next
- 7.3.3
Run continuous releases during ci-check
- 7.3.3
Address high/critical dependabot reports
- 7.3.3
Update ci.yml triggers
- 7.3.3
Exact match for renovate file name
- 7.3.3
Disable dependency update for
@material-ui/corein codemod - 7.3.3
Transpile
assertion-errorin karma tests
6 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.