See React - Major version release process for the master guidelines. You will find extra steps in these docs that are unique to MUI X.
Differences in MUI X compared to the baseline:
master
branch, we are not using the next
branch for this.v*.x
branch with the current stable version, we are not using the master
branch for this.[ ] Create a new v*.x
branch from master
with the previous major.
[ ] Open a PR to switch the npm tag from the latest
to next
[ ] Change in ./package.json
- "release:publish": "pnpm publish --recursive --tag latest",
- "release:publish:dry-run": "pnpm publish --recursive --tag latest --registry=\\"<http://localhost:4873/\\>"",
+ "release:publish": "pnpm publish --recursive --tag next",
+ "release:publish:dry-run": "pnpm publish --recursive --tag next --registry=\\"<http://localhost:4873/\\>"",
[ ] Example change in ./docs/pages/_app.js
(the function call needs to be changed on all components)
- getVersionOptions('introduction', [`v${process.env.LIB_VERSION}`, 'v6', 'v5'])
+ getVersionOptions('introduction', ['next', `v${process.env.LIB_VERSION}`, 'v6', 'v5'])
[ ] Open a PR to change the docs target in ./docs/package.json
- "deploy": "git push -f upstream master:docs-v7",
+ "deploy": "git push -f upstream master:docs-next",
/
/
/
What’s new in vX
docs page./