[code-infra] Support custom npm dist tags during release

.github/workflows/publish.yml

@@ -17,6 +17,11 @@ on:
         required: false
         type: boolean
         default: true
+      dist-tag:
+        description: 'npm dist tag to publish to'
+        required: false
+        type: string
+        default: 'latest'
 
 permissions: {}
 
@@ -48,5 +53,8 @@ jobs:
           if [ "${{ inputs.github-release }}" = "true" ]; then
             ARGS="$ARGS --github-release"
           fi
+          if [ -n "${{ inputs.dist-tag }}" ]; then
+            ARGS="$ARGS --tag ${{ inputs.dist-tag }}"
+          fi
 
           pnpm code-infra publish $ARGS

docs/package.json

@@ -6,7 +6,7 @@
     "build": "rimraf ./export && cross-env NODE_ENV=production NODE_OPTIONS=--max_old_space_size=8192 next build",
     "build:clean": "rimraf .next && pnpm build",
     "dev": "next dev --port 3005",
-    "deploy": "git push -f upstream master:docs-v1",
+    "deploy": "git fetch upstream master && git push -f upstream FETCH_HEAD:docs-v1",
     "serve": "serve ./export -l 3010",
     "typescript": "tsc -b tsconfig.json",
     "link-check": "tsx ./scripts/reportBrokenLinks.mts",

package.json

@@ -62,7 +62,7 @@
     "@arethetypeswrong/cli": "^0.18.2",
     "@babel/plugin-transform-react-constant-elements": "^7.27.1",
     "@base-ui-components/monorepo-tests": "workspace:*",
-    "@mui/internal-code-infra": "^0.0.3-canary.17",
+    "@mui/internal-code-infra": "^0.0.3-canary.19",
     "@mui/internal-test-utils": "^2.0.10",
     "@mui/monorepo": "github:mui/material-ui#v7.3.2",
     "@octokit/rest": "^22.0.0",

scripts/README.md

@@ -35,10 +35,11 @@ A typical release goes like this:
 1. Go to the [publish action](https://github.com/mui/base-ui/actions/workflows/publish.yml).
 2. Choose "Run workflow" dropdown
 
-> **Branch:** master
-> **Commit SHA to release from:** the commit that contains the merged release on master. This commit is linked to the GitHub release.
-> **Run in dry-run mode:** Used for debugging.
-> **Create GitHub release:** Keep selected if you want a GitHub release to be automatically created from the changelog.
+   > - **Branch:** master
+   > - **Commit SHA to release from:** the commit that contains the merged release on master. This commit is linked to the GitHub release.
+   > - **Run in dry-run mode:** Used for debugging.
+   > - **Create GitHub release:** Keep selected if you want a GitHub release to be automatically created from the changelog.
+   > - **npm dist tag to publish to** Use to publish legacy or canary versions.
 
 3. Click "Run workflow"
 4. Refresh the page to see the newly created workflow, and click it.