chore: release 11.3.0 #8150

github-actions · 2025-03-07T16:42:55Z

🤖 I have created a release beep boop

11.3.0

11.3.0 (2025-04-08)

Features

b306d25 #8129 add node-gyp as actual config (@wraithgar)

arborist: 9.0.2

9.0.2 (2025-04-08)

Bug Fixes

a96d8f6 #8184 arborist: omit failed optional dependencies from installed deps (fix(arborist): omit failed optional dependencies from installed deps #8184) (@owlstronaut, @zkat)
04f53ce #8180 arborist: safely fallback on unresolved $ dependency references (fix(arborist): safely fallback on unresolved $ dependency references #8180) (@owlstronaut)
885accd #8185 arborist: only replace hostname for resolved URL (fix(arborist): only replace hostname for resolved URL #8185) (@billy-briggs-dev)
8b7bb12 #8168 arborist: Allow downgrades to hoisted version dedupe workspace i… (fix(arborist): Allow downgrades to hoisted version dedupe workspace i… #8168) (@owlstronaut)
1642556 #8160 arborist: workspaces respect overrides on subsequent installs (fix(arborist): workspaces respect overrides on subsequent installs #8160) (@owlstronaut)

Chores

88a7b52 #8174 add load-virtual and reify tests for workspace override test coverage (chore: add load-virtual and reify tests for workspace override test coverage #8174) (@owlstronaut, @TrevorBurnham)

config: 10.2.0

10.2.0 (2025-04-08)

Features

b306d25 #8129 add node-gyp as actual config (@wraithgar)

Bug Fixes

9e73338 #8129 warn on non-default npm-version (@wraithgar)
1814b45 #8145 re-add positional arg and abbrev warnings (fix: re-add positional arg and abbrev warnings #8145) (@wraithgar)

libnpmdiff: 8.0.2

Dependencies

workspace: @npmcli/[email protected]

libnpmexec: 10.1.1

10.1.1 (2025-04-08)

Bug Fixes

386f328 #8154 npx: always save true when installing to npx cache (fix(npx): always save true when installing to npx cache #8154) (@milaninfy)

Dependencies

workspace: @npmcli/[email protected]

libnpmfund: 7.0.2

Dependencies

workspace: @npmcli/[email protected]

libnpmpack: 9.0.2

Dependencies

workspace: @npmcli/[email protected]

This PR was generated with Release Please. See documentation.

github-actions · 2025-03-07T16:43:03Z

Release Manager

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

Release Checklist for v11.3.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 8150 --force
```
```
npm run resetdeps
```
```
node scripts/git-dirty.js
```
2. Check CI status
```
gh pr checks --watch
```
3. Publish the CLI and workspaces

Warning:
This will publish all updated workspaces to latest, prerelease or backport depending on their version, and will publish the CLI with the dist-tag set to next-11.

Note:
The --test argument can optionally be omitted to run the publish process without running any tests locally.
```
node scripts/publish.js --test
```

4. Optionally install and test [email protected] locally

npm i -g [email protected]

npm --version
npm whoami
npm help install
# etc

5. Set latest dist-tag to newly published version

Warning:
NOT FOR PRERELEASE: Do not run this step for prereleases or if 11 is not being set to latest.
```
node . dist-tag add [email protected] latest
```

6. Trigger docs.npmjs.com update

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

7. Approve and Merge release PR

gh pr review --approve

gh pr merge --rebase

git checkout latest

git fetch

git reset --hard origin/latest

node . run resetdeps

8. Wait For Release Tags

Warning:
The remaining steps all require the GitHub tags and releases to be created first. These are done once this PR has been labelled with autorelease: tagged.

Release Please will run on the just merged release commit and create GitHub releases and tags for each package. The release bot will will comment on this PR when the releases and tags are created.

Note:
The release workflow also includes the Node integration tests which do not need to finish before continuing.

You can watch the release workflow in your terminal with the following command:
```
gh run watch `gh run list -R npm/cli -w release -b latest -L 1 --json databaseId -q ".[0].databaseId"`
```
9. Mark GitHub Release as latest

Warning:
You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

Release Please will make GitHub Releases for the CLI and all workspaces, but GitHub has UI affordances for which release should appear as the "latest", which should always be the CLI. To mark the CLI release as latest run this command:
```
gh release -R npm/cli edit v11.3.0 --latest
```
10. Open nodejs/node PR to update npm to latest

Warning:
You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

Trigger the Create Node PR action. This will open a PR on nodejs/node to the main branch.

Note:
The resulting PR may need to be labelled if it is not intended to land on old Node versions.

First, sync our fork of node with the upstream source:
```
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 -f spec=next-11
```
If the PR should be opened on a different branch (such as when doing backports) then run it with -f branch=<BRANCH_NAME>. There is also a shortcut to target a specific Node version by specifying a major version number with -f branch=18 (or similar).

For example, this will create a PR on nodejs/node to the v16.x-staging branch:
```
gh workflow run create-node-pr.yml -f spec=next-11 -f branch=16
```
11. Label and fast-track nodejs/node PR

Note:
This requires being a nodejs collaborator. This could be you!
- 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

github-actions · 2025-04-08T18:24:01Z

🤖 Created releases:

🌻

github-actions · 2025-04-08T18:24:17Z

Release Workflow

🚨🚨🚨

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

🚨🚨🚨

The `--no-package-lock` workaround was added due to npm bug #4828, where npm < 11.3.0 generates incomplete lockfiles for packages with optional platform dependencies (esbuild, rollup). Optional cross-platform dependencies were restored to `package-lock.json` in 358f276, so npm will be able to install from the lock file in the GitHub Actions. Also, fixed in npm 11.3.0 (Apr 2025), but Node v22 ships npm v10 and will remain affected out-of-the-box. Investigation notes follow. What happened? -------------- 1. Switch from yarn to npm: `package-lock.json` added, `yarn.lock` removed - modelcontextprotocol@702f827 Presumably: - run `npm install` to generate a `package-lock.json` from the yarn-managed `node_modules`, on macos - bug #4828: npm omitted optional cross-platform dependencies from the lock file 2. Pull 47, tries `npm ci`, and reverts, on 11 Nov 2024 modelcontextprotocol@3789ef9 - "Try restoring npm ci" --> testing the new node release for the bug? - ran against `setup-node`, `node-version: 18`, likely: 18.20.5 (released nov 11, 2024; ~same day) - git show 3789ef9:.github/workflows/main.yml - Failed action, and logs have expired - https://github.com/modelcontextprotocol/inspector/actions/runs/11782443393/job/32817472448 - https://nodejs.org/en/download/archive/v18.20.5 - uses npm 10.8.2 - Re-tried in inspector fork - workflow run at 3789ef9 - change `node-version: 18` to `18.20.5` (exact node / npm on commit date) - Fails due to missing `linux-x64-gnu` platform dep (rollup, would similarly affect esbuild) 3. Cross-platform dependencies restored to lockfile on 1 May 2025 modelcontextprotocol#372 - modelcontextprotocol@358f276 - worked because `package-lock.json` and `node_modules` were both removed - i.e., not the bug conditions -> even npm < 11.3.0 generates correct lockfile - At that point, `--no-package-lock` could've been removed from CI, Dockerfile, etc. NPM --- npm (aborist) fixed #4828 npm/cli#8184 - npm/cli#4828 --> frequent http 500, due to many comments - npm/cli@a96d8f6 - will not be backported Released in 11.3.0 on 8 Apr npm/cli#8150 - https://github.com/npm/cli/releases/tag/v11.3.0 - arborist 9.0.2 - https://github.com/npm/cli/releases/tag/arborist-v9.0.2 - npm v11.3.0 ships with node v24.2.0, on 6 May 2025 - https://nodejs.org/en/download/archive/v24 Node v22 ships npm v10 - https://nodejs.org/en/download/archive/v22 - will always be affected, no backport coming

The `--no-package-lock` workaround was added due to npm bug #4828, where npm < 11.3.0 generates incomplete lockfiles for packages with optional platform dependencies (esbuild, rollup). Optional cross-platform dependencies were restored to `package-lock.json` in 358f276, so npm will be able to install from the lock file in the GitHub Actions. Also, fixed in npm 11.3.0 (Apr 2025), but Node v22 ships npm v10 and will remain affected out-of-the-box. Investigation notes follow. What happened? -------------- 1. Switch from yarn to npm: `package-lock.json` added, `yarn.lock` removed - modelcontextprotocol@702f827 Presumably: - run `npm install` to generate a `package-lock.json` from the yarn-managed `node_modules`, on macos - bug #4828: npm omitted optional cross-platform dependencies from the lock file npm can't easily fix this. `npm install [email protected]` could write a resolved dependency, but at the exact version so `foo` would be pinned, and semver operator twiddling would be required to restore it as-was. The fix would be to "manually" re-add the missing metadata. 2. Pull 47, tries `npm ci`, and reverts, on 11 Nov 2024 modelcontextprotocol@3789ef9 - "Try restoring npm ci" --> testing the new node release for the bug? - ran against `setup-node`, `node-version: 18`, likely: 18.20.5 (released nov 11, 2024; ~same day) - git show 3789ef9:.github/workflows/main.yml - Failed action, and logs have expired - https://github.com/modelcontextprotocol/inspector/actions/runs/11782443393/job/32817472448 - https://nodejs.org/en/download/archive/v18.20.5 - uses npm 10.8.2 - Re-tried in inspector fork - workflow run at 3789ef9 - change `node-version: 18` to `18.20.5` (exact node / npm on commit date) - Fails due to missing `linux-x64-gnu` platform dep (rollup, would similarly affect esbuild) 3. Cross-platform dependencies restored to lockfile on 1 May 2025 modelcontextprotocol#372 - modelcontextprotocol@358f276 - worked because `package-lock.json` and `node_modules` were both removed - i.e., not the bug conditions -> even npm < 11.3.0 generates correct lockfile - At that point, `--no-package-lock` could've been removed from CI, Dockerfile, etc. NPM --- npm (aborist) fixed #4828 npm/cli#8184 - npm/cli#4828 --> frequent http 500, due to many comments - npm/cli@a96d8f6 - will not be backported Released in 11.3.0 on 8 Apr npm/cli#8150 - https://github.com/npm/cli/releases/tag/v11.3.0 - arborist 9.0.2 - https://github.com/npm/cli/releases/tag/arborist-v9.0.2 - npm v11.3.0 ships with node v24.2.0, on 6 May 2025 - https://nodejs.org/en/download/archive/v24 Node v22 ships npm v10 - https://nodejs.org/en/download/archive/v22 - will always be affected, no backport coming

github-actions bot requested a review from a team as a code owner March 7, 2025 16:42

github-actions bot added the autorelease: pending label Mar 7, 2025

github-actions bot force-pushed the release-please--branches--latest branch from c0773db to 900b40b Compare March 7, 2025 16:43

github-actions bot changed the title ~~chore: release 11.2.1~~ chore: release 11.3.0 Mar 7, 2025

github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from dde087d to d9957bb Compare March 11, 2025 21:34

wraithgar mentioned this pull request Mar 12, 2025

[BUG] The npm_config_node_gyp environment variable and npm config set node-gyp config don't work with npm 7 npm/run-script#23

Closed

github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from 5586bf2 to 90a987f Compare March 13, 2025 03:14

github-actions bot force-pushed the release-please--branches--latest branch 8 times, most recently from 611b9a5 to f5dc19b Compare March 25, 2025 21:33

github-actions bot force-pushed the release-please--branches--latest branch 6 times, most recently from dc5caab to da1d171 Compare March 27, 2025 14:31

owlstronaut force-pushed the latest branch 2 times, most recently from 85ec0c9 to 26b6454 Compare March 27, 2025 18:03

github-actions bot force-pushed the release-please--branches--latest branch 6 times, most recently from 5b3e1e7 to b150799 Compare April 3, 2025 15:47

github-actions bot force-pushed the release-please--branches--latest branch from b150799 to d1492e5 Compare April 8, 2025 02:22

chore: release 11.3.0

0e3ff80

github-actions bot force-pushed the release-please--branches--latest branch from d1492e5 to 0e3ff80 Compare April 8, 2025 02:23

owlstronaut approved these changes Apr 8, 2025

View reviewed changes

owlstronaut merged commit 5bd086b into latest Apr 8, 2025
22 checks passed

owlstronaut deleted the release-please--branches--latest branch April 8, 2025 18:20

github-actions bot added autorelease: tagged and removed autorelease: pending labels Apr 8, 2025

damienwebdev mentioned this pull request May 29, 2025

The Nx Daemon is unsupported in WebAssembly environments nrwl/nx#27263

Open

4 tasks

damienwebdev mentioned this pull request Sep 30, 2025

build: add support for mac devices graycoreio/daffodil#4046

Merged

15 tasks

Fuzzy3 mentioned this pull request Dec 9, 2025

Housekeeping: Use npm ci when setting up the environment kirbydesign/designsystem#4190

Merged

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: release 11.3.0 #8150

chore: release 11.3.0 #8150

Uh oh!

github-actions bot commented Mar 7, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Mar 7, 2025 •

edited

Loading

Uh oh!

Uh oh!

github-actions bot commented Apr 8, 2025

Uh oh!

github-actions bot commented Apr 8, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore: release 11.3.0 #8150

chore: release 11.3.0 #8150

Uh oh!

Conversation

github-actions bot commented Mar 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 I have created a release beep boop

11.3.0 (2025-04-08)

Features

Bug Fixes

Documentation

Dependencies

Chores

9.0.2 (2025-04-08)

Bug Fixes

Chores

10.2.0 (2025-04-08)

Features

Bug Fixes

Dependencies

10.1.1 (2025-04-08)

Bug Fixes

Dependencies

Dependencies

Dependencies

Uh oh!

github-actions bot commented Mar 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Manager

Release Checklist for v11.3.0

Uh oh!

Uh oh!

github-actions bot commented Apr 8, 2025

Uh oh!

github-actions bot commented Apr 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Workflow

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions bot commented Mar 7, 2025 •

edited

Loading

github-actions bot commented Mar 7, 2025 •

edited

Loading

github-actions bot commented Apr 8, 2025 •

edited

Loading