[internal] Prepare libraries for first v9 alpha release #47756
Conversation
silviuaavram
commented
Feb 12, 2026
silviuaavram
commented
- I have followed (at least) the PR section of the contributing guide.
There was a problem hiding this comment.
Pull request overview
This PR prepares MUI libraries for a v9 alpha release by updating documentation URLs, package versions, and adding migration documentation. However, there's a critical discrepancy: the PR title says "v7 alpha release" but all changes are for v9.
Changes:
- Updates all documentation URLs from
https://mui.comtohttps://next.mui.comfor the v9 alpha pre-release - Changes package installation instructions from
@latestto@nexttags across all documentation - Updates internal workspace dependencies from
workspace:^toworkspace:*for packages releasing together in v9 - Adds v9 migration guide documentation and updates version selectors to include v7 as a previous version
Reviewed changes
Copilot reviewed 83 out of 84 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/mui-system/src/createBreakpoints/createBreakpoints.d.ts | Updates API documentation URLs to next.mui.com domain |
| packages/mui-system/src/Grid/deleteLegacyGridProps.ts | Updates error message URL to next.mui.com |
| packages/mui-system/src/Grid/Grid.test.js | Updates test expectation to match error message URL change |
| packages/mui-system/package.json | Updates workspace dependencies to use * version for v9 release |
| packages/mui-system/README.md | Updates install command to use @next tag and documentation URL |
| packages/mui-styled-engine/README.md | Updates documentation URL to next.mui.com |
| packages/mui-styled-engine-sc/README.md | Updates documentation URL to next.mui.com |
| packages/mui-private-theming/package.json | Updates @mui/utils workspace dependency version |
| packages/mui-material/src/styles/createThemeNoVars.js | Updates error message documentation URL |
| packages/mui-material/package.json | Updates workspace dependencies for v9 release |
| packages/mui-material/README.md | Updates install command and documentation URL |
| packages/mui-lab/package.json | Updates workspace dependencies for v9 release |
| packages/mui-lab/README.md | Updates install commands and documentation URL |
| packages/mui-icons-material/package.json | Updates workspace dependency versions |
| packages/mui-icons-material/README.md | Updates install commands and documentation URLs |
| packages/mui-docs/README.md | Updates install commands to use @next tag |
| packages/mui-codemod/README.md | Updates all codemod command examples to use @next tag |
| packages/api-docs-builder-core/materialUi/projectSettings.ts | Updates base API URL to next.mui.com |
| examples/*/package.json (multiple) | Updates @mui packages to use "next" version in all examples |
| examples/*/README.md (multiple) | Updates documentation URLs to next.mui.com |
| docs/translations/translations.json | Adds v9 upgrade translations |
| docs/src/modules/sandbox/*.test.js | Updates test expectations for @next package versions |
| docs/src/modules/sandbox/Dependencies.ts | Changes default npm tag from "latest" to "next" |
| docs/src/modules/components/Head.tsx | Updates canonical URL host to next.mui.com |
| docs/pages/system/migration/upgrade-to-v9.js | Adds v9 migration page component |
| docs/pages/material-ui/migration/upgrade-to-v9.js | Adds v9 migration page component |
| docs/pages/_app.js | Adds v7 to version selectors for Material UI and System |
| docs/package.json | Updates deploy script to push to "next" branch; updates workspace dependencies |
| docs/data/system/pages.ts | Adds v9 upgrade page to System navigation |
| docs/data/system/migration/migration-to-v9/migration-to-v9.md | Creates System v9 migration guide |
| docs/data/system/getting-started/installation/installation.md | Updates install commands to use @next tag |
| docs/data/material/pages.ts | Adds v9 upgrade section to Material UI navigation |
| docs/data/material/migration/upgrade-to-v7/upgrade-to-v9/upgrade-to-v9.md | Creates Material UI v9 migration guide (incorrect path) |
| docs/data/material/migration/upgrade-to-v7/*.md | Updates codemod commands to use @next tag |
| docs/data/material/integrations/styled-components/styled-components.md | Updates package resolution examples to use @next tag |
| docs/data/material/getting-started/templates/*/README.md | Updates demo URLs to next.mui.com |
| docs/data/material/getting-started/support/support.md | Adds v9.0.0 to supported versions table |
| docs/data/material/getting-started/installation/installation.md | Updates install commands to use @next tag |
| docs/data/material/components/number-field/number-field.md | Removes npm-tag-reference comment |
| docs/data/material/components/material-icons/material-icons.md | Updates install commands to use @next tag |
| docs/data/material/components/icons/icons.md | Updates install commands to use @next tag |
| docs/data/material/components/about-the-lab/about-the-lab.md | Updates install commands to use @next tag |
| README.md | Updates logo and homepage URL to next.mui.com |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Installation | ||
|
|
||
| <!-- #npm-tag-reference --> | ||
|
|
||
| <codeblock storageKey="package-manager"> |
There was a problem hiding this comment.
The removal of the "npm-tag-reference" comment before the Installation section is inconsistent with similar sections in other files where this comment is being added or retained. Based on the PR's pattern of adding "@next" tags, this comment should likely be retained here for consistency, especially since Base UI installation instructions may also need version tags in the future.
| "build-sw": "node ./scripts/buildServiceWorker.js", | ||
| "dev": "next dev", | ||
| "deploy": "git fetch upstream master && git push -f material-ui-docs FETCH_HEAD:latest", | ||
| "deploy": "git fetch upstream master && git push -f material-ui-docs FETCH_HEAD:next", |
There was a problem hiding this comment.
The deploy script has been changed from pushing to "latest" branch to pushing to "next" branch. This aligns with the pre-release strategy, but ensure that the "next" branch exists and is properly configured in the deployment infrastructure. Also verify that this change is intentional and won't disrupt the normal deployment workflow.
| # Upgrade to v9 | ||
|
|
||
| <p class="description">This guide explains how to upgrade from Material UI v7 to v9.</p> | ||
|
|
||
| ## Start using the alpha release | ||
|
|
||
| In the `package.json` file, change the package version from `latest` to `next`. | ||
|
|
||
| ```diff title="package.json" | ||
| -"@mui/material": "latest", | ||
| +"@mui/material": "next", | ||
| ``` | ||
|
|
||
| Using `next` ensures your project always uses the latest v9 pre-releases. | ||
| Alternatively, you can also target and fix it to a specific version, for example, `9.0.0-alpha.0`. | ||
|
|
||
| ## Breaking changes | ||
|
|
||
| Since v9 is a new major release, it contains some changes that affect the public API. | ||
| The steps you need to take to migrate from Material UI v7 to v9 are described below. | ||
|
|
||
| :::info | ||
| This list is a work in progress. | ||
| Expect updates as new breaking changes are introduced. | ||
| ::: |
There was a problem hiding this comment.
The file path contains "upgrade-to-v7" as a parent directory, but the file is about upgrading to v9. This appears to be an incorrect directory structure. The file should likely be at "docs/data/material/migration/upgrade-to-v9/upgrade-to-v9.md" instead of "docs/data/material/migration/upgrade-to-v7/upgrade-to-v9/upgrade-to-v9.md".
| - "@mui/styled-engine": "@next" | ||
| + "@mui/styled-engine": "npm:@mui/styled-engine-sc@next" |
There was a problem hiding this comment.
In the styled-components integration documentation, the package version syntax has been changed to use "@next" without the "npm:" prefix on one line, but keeps the "npm:" prefix on the resolutions line. This creates inconsistency. Both should use "npm:@mui/styled-engine-sc@next" for clarity and consistency, or if the npm: prefix is unnecessary in the dependencies field, the comment should explain this difference.
| "@mui/private-theming": "workspace:*", | ||
| "@mui/styled-engine": "workspace:*", | ||
| "@mui/types": "workspace:^", | ||
| "@mui/utils": "workspace:^", | ||
| "@mui/utils": "workspace:*", |
There was a problem hiding this comment.
There's an inconsistency in workspace dependency versioning. Some dependencies are changed from "workspace:^" to "workspace:" (like @mui/utils, @mui/system, @mui/styled-engine), while @mui/types remains at "workspace:^". This inconsistency should be addressed - either all internal dependencies should use the same pattern, or there should be a clear reason for the difference. The pattern suggests that packages being released as part of v9 should use "workspace:" while others remain at "workspace:^", but this should be consistently applied.
| <!-- markdownlint-disable-next-line --> | ||
| <p align="center"> | ||
| <a href="https://mui.com/core/" rel="noopener" target="_blank"><img width="150" height="133" src="https://mui.com/static/logo.svg" alt="Material UI logo"></a> | ||
| <a href="https://next.mui.com/core/" rel="noopener" target="_blank"><img width="150" height="133" src="https://next.mui.com/static/logo.svg" alt="Material UI logo"></a> |
There was a problem hiding this comment.
The logo src URL has been updated to use "next.mui.com", but this may cause issues if the logo SVG file doesn't exist at that location yet. Verify that the logo file is accessible at "https://next.mui.com/static/logo.svg" before merging this change.
| <a href="https://next.mui.com/core/" rel="noopener" target="_blank"><img width="150" height="133" src="https://next.mui.com/static/logo.svg" alt="Material UI logo"></a> | |
| <a href="https://next.mui.com/core/" rel="noopener" target="_blank"><img width="150" height="133" src="https://mui.com/static/logo.svg" alt="Material UI logo"></a> |
| @@ -0,0 +1,25 @@ | |||
| # Upgrade to v9 | |||
There was a problem hiding this comment.
The PR title says "Prepare libraries for first v7 alpha release" but the changes are actually preparing for a v9 alpha release. The migration guides, version selectors, and documentation all reference v9, not v7. The title should be updated to match the actual changes being made.
| # Upgrade to v9 | ||
|
|
||
| <p class="description">This guide explains how to upgrade from MUI System v7 to v9.</p> | ||
|
|
||
| ## Start using the alpha release | ||
|
|
||
| In the `package.json` file, change the package version from `latest` to `next`. | ||
|
|
||
| ```diff title="package.json" | ||
| -"@mui/system": "latest", | ||
| +"@mui/system": "next", | ||
| ``` | ||
|
|
||
| Using `next` ensures your project always uses the latest v9 pre-releases. | ||
| Alternatively, you can also target and fix it to a specific version, for example, `9.0.0-alpha.0`. | ||
|
|
||
| ## Breaking changes | ||
|
|
||
| Since v9 is a new major release, it contains some changes that affect the public API. | ||
| The steps you need to take to migrate from MUI System v7 to v9 are described below. | ||
|
|
||
| :::info | ||
| This list is a work in progress. | ||
| Expect updates as new breaking changes are introduced. | ||
| ::: |
There was a problem hiding this comment.
The migration guide file is named "migration-to-v9" in the directory name but the actual markdown file is called "migration-to-v9.md". However, in the System pages configuration and imports, it references "upgrade-to-v9". This naming inconsistency should be resolved - the directory should likely be named "upgrade-to-v9" instead of "migration-to-v9" to match the pattern used elsewhere.
ZeeshanTamboli
changed the title
zannager
added
the
internal
2 participants
