You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.
gh pr checkout 8332 --force
npm run resetdeps
node scripts/git-dirty.js
2. Check CI status
gh pr checks --watch
3. Publish the CLI and workspaces
Warning:
This will publish all updated workspaces to latest, prerelease or backport depending on their version, and will publish the CLI with the dist-tag set to next-11.
Note:
The --test argument can optionally be omitted to run the publish process without running any tests locally.
node scripts/publish.js --test
4. Optionally install and test npm@11.4.2 locally
npm i -g npm@11.4.2
npm --version
npm whoami
npm help install
# etc
5. Set latestdist-tag to newly published version
Warning:
NOT FOR PRERELEASE: Do not run this step for prereleases or if 11 is not being set to latest.
node . dist-tag add npm@11.4.2 latest
6. Trigger docs.npmjs.com update
gh workflow run update-cli.yml --repo npm/documentation
7. Approve and Merge release PR
gh pr review --approve
gh pr merge --rebase
git checkout latest
git fetch
git reset --hard origin/latest
node . run resetdeps
8. Wait For Release Tags
Warning:
The remaining steps all require the GitHub tags and releases to be created first. These are done once this PR has been labelled with autorelease: tagged.
Release Please will run on the just merged release commit and create GitHub releases and tags for each package. The release bot will will comment on this PR when the releases and tags are created.
Note:
The release workflow also includes the Node integration tests which do not need to finish before continuing.
You can watch the release workflow in your terminal with the following command:
gh run watch `gh run list -R npm/cli -w release -b latest -L 1 --json databaseId -q ".[0].databaseId"`
9. Mark GitHub Release as latest
Warning:
You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.
Release Please will make GitHub Releases for the CLI and all workspaces, but GitHub has UI affordances for which release should appear as the "latest", which should always be the CLI. To mark the CLI release as latest run this command:
gh release -R npm/cli edit v11.4.2 --latest
10. Open nodejs/node PR to update npm to latest
Warning:
You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.
Trigger the Create Node PR action. This will open a PR on nodejs/node to the main branch.
Note:
The resulting PR may need to be labelled if it is not intended to land on old Node versions.
First, sync our fork of node with the upstream source:
Then, if we are opening a PR against the latest version of node:
gh workflow run create-node-pr.yml -f spec=next-11
If the PR should be opened on a different branch (such as when doing backports) then run it with -f branch=<BRANCH_NAME>. There is also a shortcut to target a specific Node version by specifying a major version number with -f branch=18 (or similar).
For example, this will create a PR on nodejs/node to the v16.x-staging branch:
gh workflow run create-node-pr.yml -f spec=next-11 -f branch=16
11. Label and fast-track nodejs/node PR
Note:
This requires being a nodejs collaborator. This could be you!
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
11.4.2
11.4.2 (2025-05-27)
Bug Fixes
e758dd7#8318 powershell: multiple Invoke-Expression fixes (fix(powershell): multiple Invoke-Expression fixes #8318) (@alexsch01)Documentation
8b55d38#8329 Rename "command" to "script" (docs: Rename "command" to "script" #8329) (@DanKaplanSES)This PR was generated with Release Please. See documentation.