Packages

@mui/utils

9.5.0 · 9 Oct 2026MIT21.2M / weekRepositoryHomepagenpmAtom feed

Upgrading @mui/utils From 7.1.0 to 7.1.1

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 7.1.0Newest 7.x7.3.11Latest9.5.0
  1. 7.1.0yours
  2. 7.1.1target
1
change to make
0
advisories fixed
2
new
2
fixes

Before you upgrade

Tick each one off as you go
  • Breaking7.1.1

Release by release

  1. 7.1.1

    Migration needed2 Jun 20252 new · 2 fixes
    • Breaking

      Remove deprecated TransitionComponent from demo

    • New

      Add plugin to check for index file access

    • New

      Add comment that lab should be in alpha

    • Fixed

      Avoid loading barrel file during type checking

    • Fixed

      Avoid running continuous release on forks

12 other lines we could not sort, mostly version bumps
  • Move packages to mui/mui-public

    7.1.1
  • Move chai to peerDep

    7.1.1
  • Remove unnecessary ref from HighlightedCode component

    7.1.1
  • Import mocha type instead of global

    7.1.1
  • Dependabot also create branches

    7.1.1
  • Remove checkout job altogether

    7.1.1
  • Remove required checkout workflows in circleci

    7.1.1
  • Run pnpm docs:sync-team

    7.1.1
  • Upgrade MUI X packages to v8

    7.1.1
  • Minor detail to reduce confusion

    7.1.1

11 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.