chore: release 11.20.0 - #9922

Open
github-actions[bot] wants to merge 1 commit into
release/v11from
release-please--branches--release/v11
Open

chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from
release-please--branches--release/v11

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 27, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

11.20.0

11.20.0 (2026-08-28)

Features

Bug Fixes

Chores

Dependencies

arborist: 9.9.2

9.9.2 (2026-08-28)

Bug Fixes

Chores

libnpmdiff: 8.1.13

Dependencies

libnpmexec: 10.3.3

Dependencies

libnpmfund: 7.0.27

Dependencies

libnpmpack: 9.1.14

Dependencies

This PR was generated with Release Please. See documentation.

@github-actions
github-actionsBot requested a review from a team as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot requested a review from a team as a code ownerAugust 27, 2026 21:07
@github-actions

github-actionsBot commented Aug 27, 2026•
edited
Loading

Copy link
Copy Markdown
ContributorAuthor

Release Manager

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

Release Checklist for v11.20.0

  • 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 9922 --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.20.0 locally

    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc

  • 6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest

  • 11. Open nodejs/node PR to update npm

    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.

    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

    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.

    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included

Release Checklist for v11.20.0

  • 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 9922 --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.20.0 locally

    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc

  • 6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest

  • 11. Open nodejs/node PR to update npm

    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.

    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

    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.

    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included

Release Checklist for v11.20.0

  • 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 9922 --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.20.0 locally

    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc

  • 6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest

  • 11. Open nodejs/node PR to update npm

    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.

    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

    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.

    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included

Release Checklist for v11.20.0

  • 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 9922 --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.20.0 locally

    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc

  • 6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest

  • 11. Open nodejs/node PR to update npm

    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.

    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

    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.

    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included

@github-actions
github-actionsBotforce-pushed the release-please--branches--release/v11 branch from 0905f03 to 0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot changed the title chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed the release-please--branches--release/v11 branch 6 times, most recently from 514e6a4 to 51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed the release-please--branches--release/v11 branch from 51db2f2 to a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants


, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
chore: release 11.20.0 - #9922
Open
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Open
chore: release 11.20.0#9922
github-actions[bot] wants to merge 1 commit into
release/v11from 
release-please--branches--release/v11
Conversation
@github-actions
@github-actionsgithub-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🤖 I have created a release beepboop
11.20.0
11.20.0 (2026-08-28)
Features
Bug Fixes
Chores
Dependencies
arborist: 9.9.2
9.9.2 (2026-08-28)
Bug Fixes
Chores
libnpmdiff: 8.1.13
Dependencies
libnpmexec: 10.3.3
Dependencies
libnpmfund: 7.0.27
Dependencies
libnpmpack: 9.1.14
Dependencies
This PR was generated with Release Please. See documentation.
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
requested a review
from a team
as a code ownerAugust 27, 2026 21:07
@github-actions
github-actionsBot
commented
Aug 27, 2026•

edited

Loading

Copy link


Copy Markdown

ContributorAuthor
Release Manager
Release workflow run: https://github.com/npm/cli/actions/runs/33197379817
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
Release Checklist for v11.20.0
  •  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 9922 --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.20.0 locally
    npm i -g npm@11.20.0
    npm --version
npm whoami
npm help install
# etc
  •  6. 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.20.0 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 release/v11
    git fetch
    git reset --hard origin/release/v11
    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 release/v11 -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.20.0 --latest
  •  11. Open nodejs/node PR to update npm
    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.
    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
    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.
    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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
0905f03 to
0b75921CompareAugust 27, 2026 21:08
@github-actionsgithub-actionsBot
changed the title
chore: release 11.19.2chore: release 11.20.0Aug 27, 2026
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
6 times, most recently
from
514e6a4 to
51db2f2CompareAugust 28, 2026 18:03
@github-actions
github-actionsBotforce-pushed
the
release-please--branches--release/v11
branch
from
51db2f2 to
a61d812CompareAugust 28, 2026 18:04
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels

autorelease: pending

Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

0 participants