Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/22198565040

Release Checklist for v11.10.1

• 1. Checkout the release branch

  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 8987 --force

  npm run resetdeps

  node scripts/git-dirty.js

• 2. Check CI status

  gh pr checks --watch

• 3. Log in to npm

  npm login sessions are short lived, so you will want to have a fresh one before you publish.

  npm login

• 4. 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

• 5. Optionally install and test npm@11.10.1 locally

  npm i -g npm@11.10.1

  npm --version
  npm whoami
  npm help install
  # etc

• 6. Set latest dist-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.10.1 latest

• 7. Trigger docs.npmjs.com update

  gh workflow run update-cli.yml --repo npm/documentation

• 8. 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

• 9. 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"`
  

• 10. 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.10.1 --latest

• 11. 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:

  gh repo sync npm/node --source nodejs/node --force

  Then, if we are opening a PR against the latest version of node:

  gh workflow run create-node-pr.yml -R npm/cli -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 -R npm/cli -f spec=next-11 -f branch=16

• 12. Label and fast-track nodejs/node PR

  Note:
  This requires being a nodejs collaborator. This could be you!

  • Thumbs-up reaction on the Fast-track comment
  • Add an LGTM / Approval
  • Add request-ci label to get it running CI
  • Add commit-queue label once everything is green

Should fix #8992

what about bc break #8981? shouldnt the release wait for that?

I think #8992 is bad enough that this release should just go out right away without waiting. My project can’t deploy at all given our organization security rules.

#8981 has a workaround, so let it get on the next train without this one waiting, IMHO.

I know that each person has their own angle based on what is blocking them, though, so I have to recognize I may have a bias here 🤷‍♂️.

🤖 Created releases:

• v11.10.1
• arborist-v9.3.1
• config-v10.7.1
• libnpmdiff-v8.1.2
• libnpmexec-v10.2.2
• libnpmfund-v7.0.16
• libnpmpack-v9.1.2

🌻

Release Workflow

• npm@11.10.1 https://github.com/npm/cli/releases/tag/v11.10.1
• @npmcli/arborist@9.3.1 https://github.com/npm/cli/releases/tag/arborist-v9.3.1
• @npmcli/config@10.7.1 https://github.com/npm/cli/releases/tag/config-v10.7.1
• libnpmdiff@8.1.2 https://github.com/npm/cli/releases/tag/libnpmdiff-v8.1.2
• libnpmexec@10.2.2 https://github.com/npm/cli/releases/tag/libnpmexec-v10.2.2
• libnpmfund@7.0.16 https://github.com/npm/cli/releases/tag/libnpmfund-v7.0.16
• libnpmpack@9.1.2 https://github.com/npm/cli/releases/tag/libnpmpack-v9.1.2
• Workflow run: ❌ https://github.com/npm/cli/actions/runs/22201970732

🚨🚨🚨

@npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output.

🚨🚨🚨