chore: release 11.0.0-pre.0 #7813

github-actions · 2024-10-03T18:16:25Z

🤖 I have created a release beep boop

11.0.0-pre.0

11.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

When publishing a package with a pre-release version, you must explicitly specify a tag.
--ignore-scripts now applies to all lifecycle scripts, include prepare
npm will no longer fall back to the old audit endpoint if the bulk advisory request fails.
npm will no longer switch to global mode if aliased to "npmg" or "npm-g" etc.
The npm hook command has been removed
Attestations made by this package will no longer validate in npm versions prior to 10.6.0
npm now supports node ^20.17.0 || >=22.9.0
@npmcli/docs now supports node ^20.17.0 || >=22.9.0

Features

6995303 #7850 adds --ignore-scripts flag to pack (@reggi)

arborist: 9.0.0-pre.0

9.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

--ignore-scripts now applies to all lifecycle scripts, include prepare
npm will no longer fall back to the old audit endpoint if the bulk advisory request fails.
@npmcli/arborist now supports node ^20.17.0 || >=22.9.0

Features

6995303 #7850 adds --ignore-scripts flag to pack (@reggi)

Bug Fixes

080a0f2 #7911 remove old audit fallback request (@wraithgar)
3ffc08b #7831 for @npmcli/arborist sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

7dbef6f #7850 [email protected]
75a3f12 #7859 remove unused deps (deps: remove unused deps #7859)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

config: 10.0.0-pre.0

10.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

@npmcli/config now supports node ^20.17.0 || >=22.9.0

Bug Fixes

6e11eb2 #7831 for @npmcli/config sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

libnpmaccess: 10.0.0-pre.0

10.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmaccess now supports node ^20.17.0 || >=22.9.0

Bug Fixes

687cfaf #7831 for libnpmaccess sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

75a3f12 #7859 remove unused deps (deps: remove unused deps #7859)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

libnpmdiff: 8.0.0-pre.0

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmdiff now supports node ^20.17.0 || >=22.9.0

Bug Fixes

dab3042 #7831 for libnpmdiff sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

7dbef6f #7850 [email protected]

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)
workspace: @npmcli/[email protected]

libnpmexec: 10.0.0-pre.0

10.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmexec now supports node ^20.17.0 || >=22.9.0

Bug Fixes

7f541e8 #7815 make pack and exec work with git hash refs (fix: make pack and exec work with git hash refs #7815) (@milaninfy)
2902d4c #7831 for libnpmexec sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

7dbef6f #7850 [email protected]

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)
workspace: @npmcli/[email protected]

libnpmfund: 7.0.0-pre.0

7.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmfund now supports node ^20.17.0 || >=22.9.0

Bug Fixes

44be07c #7831 for libnpmfund sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

Dependencies

workspace: @npmcli/[email protected]

libnpmorg: 8.0.0-pre.0

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmorg now supports node ^20.17.0 || >=22.9.0

Bug Fixes

62c4604 #7831 for libnpmorg sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

libnpmpack: 9.0.0-pre.0

9.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmpack now supports node ^20.17.0 || >=22.9.0

Bug Fixes

7f541e8 #7815 make pack and exec work with git hash refs (fix: make pack and exec work with git hash refs #7815) (@milaninfy)
f7b41a3 #7831 for libnpmpack sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

7dbef6f #7850 [email protected]

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)
workspace: @npmcli/[email protected]

libnpmpublish: 11.0.0-pre.0

11.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Attestations made by this package will no longer validate in npm versions prior to 10.6.0
libnpmpublish now supports node ^20.17.0 || >=22.9.0

Bug Fixes

f75da94 #7833 update libnpmpublish tests for sigstore 3.0.0 (@bdehamer)
a2f8af0 #7831 for libnpmpublish sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Dependencies

75a3f12 #7859 remove unused deps (deps: remove unused deps #7859)
7ee15bb #7833 bump sigstore from 2.x to 3.0.0 (@bdehamer)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

libnpmsearch: 9.0.0-pre.0

9.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmsearch now supports node ^20.17.0 || >=22.9.0

Bug Fixes

2f2ee15 #7831 for libnpmsearch sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

libnpmteam: 8.0.0-pre.0

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmteam now supports node ^20.17.0 || >=22.9.0

Bug Fixes

9561fa7 #7831 for libnpmteam sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

libnpmversion: 8.0.0-pre.0

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

libnpmversion now supports node ^20.17.0 || >=22.9.0

Bug Fixes

57eef8d #7831 for libnpmversion sets node engine range to ^20.17.0 || >=22.9.0 (@reggi)

Chores

6edfe2f #7937 @npmcli/[email protected] (@wraithgar)

This PR was generated with Release Please. See documentation.

github-actions · 2024-10-03T18:16:34Z

Release Manager

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

Release Checklist for v11.0.0-pre.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 7813 --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. Trigger docs.npmjs.com update

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

6. 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

7. 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"`
```
8. 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.0.0-pre.0 --latest
```
9. 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
```
10. 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 · 2024-11-26T19:49:57Z

🤖 Created releases:

🌻

github-actions · 2024-11-26T19:50:16Z

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.

🚨🚨🚨

github-actions bot requested a review from a team as a code owner October 3, 2024 18:16

github-actions bot added the autorelease: pending label Oct 3, 2024

github-actions bot force-pushed the release-please--branches--latest branch 3 times, most recently from ac8c629 to f0e208f Compare October 7, 2024 16:55

github-actions bot force-pushed the release-please--branches--latest branch 2 times, most recently from 01b6d54 to bdf8173 Compare October 11, 2024 14:14

github-actions bot changed the title ~~chore: release 10.9.1~~ chore: release 11.0.0-pre Oct 14, 2024

github-actions bot force-pushed the release-please--branches--latest branch 14 times, most recently from c52be66 to 11cae44 Compare October 18, 2024 14:42

github-actions bot force-pushed the release-please--branches--latest branch 6 times, most recently from ee0f312 to a928778 Compare November 20, 2024 22:55

github-actions bot force-pushed the release-please--branches--latest branch from a928778 to 345c0a4 Compare November 21, 2024 21:27

github-actions bot force-pushed the release-please--branches--latest branch 5 times, most recently from ba7ba98 to be89d14 Compare November 25, 2024 19:55

github-actions bot changed the title ~~chore: release 11.0.0-pre~~ chore: release 11.0.0-pre.0 Nov 26, 2024

github-actions bot force-pushed the release-please--branches--latest branch 3 times, most recently from d63ffaa to 7dd9b97 Compare November 26, 2024 17:09

chore: release 11.0.0-pre.0

1da850a

github-actions bot force-pushed the release-please--branches--latest branch from 7dd9b97 to 1da850a Compare November 26, 2024 17:10

wraithgar approved these changes Nov 26, 2024

View reviewed changes

wraithgar merged commit 523ad85 into latest Nov 26, 2024
18 checks passed

wraithgar deleted the release-please--branches--latest branch November 26, 2024 19:45

github-actions bot added autorelease: tagged and removed autorelease: pending labels Nov 26, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: release 11.0.0-pre.0 #7813

chore: release 11.0.0-pre.0 #7813

github-actions bot commented Oct 3, 2024 •

edited

Loading

github-actions bot commented Oct 3, 2024 •

edited by wraithgar

Loading

github-actions bot commented Nov 26, 2024

github-actions bot commented Nov 26, 2024 •

edited

Loading

chore: release 11.0.0-pre.0 #7813

chore: release 11.0.0-pre.0 #7813

Conversation

github-actions bot commented Oct 3, 2024 • edited Loading

🤖 I have created a release beep boop

11.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Features

Bug Fixes

Documentation

Dependencies

Chores

9.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Features

Bug Fixes

Dependencies

Chores

10.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Chores

10.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Dependencies

Chores

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Dependencies

Chores

10.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Dependencies

Chores

7.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Chores

Dependencies

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Chores

9.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Dependencies

Chores

11.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Dependencies

Chores

9.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Chores

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Chores

8.0.0-pre.0 (2024-11-26)

⚠️ BREAKING CHANGES

Bug Fixes

Chores

github-actions bot commented Oct 3, 2024 • edited by wraithgar Loading

Release Manager

Release Checklist for v11.0.0-pre.0

github-actions bot commented Nov 26, 2024

github-actions bot commented Nov 26, 2024 • edited Loading

Release Workflow

github-actions bot commented Oct 3, 2024 •

edited

Loading

github-actions bot commented Oct 3, 2024 •

edited by wraithgar

Loading

github-actions bot commented Nov 26, 2024 •

edited

Loading