<aside> ℹ️
When fixing steps in this process, please update this page template: Name vX so the next release goes more smoothly.
</aside>
The process aims to be identical for all components/repositories, but might have specificities:
Core - Major version release process
MUI X - Major version release process
We very rarely have two active branches working, only one.
[ ] Create a new GitHub label for the new major: vX.x
[ ] Create a new branch vX.x
from the current master
branch commit. Use that branch for the current major (soon to be older). e.g v8.x
if working on v9.
[ ] On the vX.x
branch, update the scripts that run the CI to use the new branch correctly.
Use #target-branch-reference
to find those (and add this tag where missing).
For example:
[ ] Make a new release of the current stable.
<aside> ⚠️
At this stage, the git repository should continue to work on the old major, e.g., build passes, nothing broken. We can make heavy changes in master
without impacting anyone.
</aside>
[ ] Add BROWSERSLIST_IGNORE_OLD_DATA
to avoid build fails for outdated browser data.
diff --git a/package.json b/package.json
index 8369616e76..f1a004a2e7 100644
--- a/package.json
+++ b/package.json
@@ -14,10 +14,10 @@
"clean:zero": "pnpm --filter \\"@pigmentcss/*\\" clean",
"build:codesandbox": "BROWSERSLIST_IGNORE_OLD_DATA=true NODE_OPTIONS=\\"--max_old_space_size=4096\\" lerna run --concurrency 8 --scope \\"@mui/*\\" --scope \\"@mui-internal/*\\" --no-private build",
"release:version": "lerna version --no-changelog --no-push --no-git-tag-version --no-private --force-publish=@mui/core-downloads-tracker",
- "release:build": "lerna run --concurrency 8 --no-private build --skip-nx-cache",
+ "release:build": "BROWSERSLIST_IGNORE_OLD_DATA=true lerna run --concurrency 8 --no-private build --skip-nx-cache",
"release:changelog": "node scripts/releaseChangelog.mjs",
master
. For example:
Until the first alpha release and beyond, please: