@mui/types
9.5.0 · 9 Oct 2026MIT19.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @mui/types From 7.2.23 to 9.5.0
21 releases in betweennotes for 7
Reading releases, release notes and advisories…
- 3+
- changes to make
- 0
- advisories fixed
- 5+
- new
- 10+
- fixes
Counted from 7 of 21 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- Breaking9.5.0
- Breaking7.3.0
- Breaking7.3.0
Release by release
- Breaking
Remove invalid
numbertype from supportedOverridableStringUniontype arguments
- Breaking
- Fixed
Fix team sync review requests
- Fixed
- Fixed
Fix caret annotation broken by Prettier wrapping
- Fixed
Fix Dependabot alerts
- Fixed
Fix team sync PR creation
- Fixed
- New
Support turbopack for docs
- Fixed
Fix immutable cache headers for /_next/static assets
- New
- New
Add
x-schedulertoMuiProductIdtype - New
Add scheduler to product switcher
- New
7.3.1 – 7.4.1214 releases, nothing new or fixed; 13 without a note
- Breaking
Remove deprecated props from demos
- Breaking
Remove comment saving in G-sheet option
- New
Add
@base-ui-components/*to env info - New
Add instructions for patch release
- Breaking
7.2.24no release note
34 other lines we could not sort, mostly version bumps
- 9.4.0
♿️ Opt in to a consistent keyboard focus ring across components with the new
theme.focusVisible. - 9.4.0
♿️ The Tooltip now supports disabled button triggers without an extra wrapper element.
- 9.4.0
Import the test globals from vitest
- 9.4.0
Point the support validator link at frontend-public
- 9.4.0
Update CircleCI orb
- 9.4.0
Use ESM current directory syntax for Vitest config
- 9.4.0
Use @typescript/typescript6 for the docs tooling
- 9.4.0
Remove the
globalSelectorstylis middleware - 9.3.0
♿️ Keyboard navigation in the Toggle Button Group now follows the roving tabindex pattern.
- 9.3.0
♿️ The Autocomplete announces its loading and no options messages through a new
statusslot.
61 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.