You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 7777 --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-10.
Note:
The --test argument can optionally be omitted to run the publish process without running any tests locally.
node scripts/publish.js --test
4. Optionally install and test npm@10.9.0 locally
npm i -g npm@10.9.0
npm --version
npm whoami
npm help install
# etc
5. Set latestdist-tag to newly published version
Warning:
NOT FOR PRERELEASE: Do not run this step for prereleases or if 10 is not being set to latest.
node . dist-tag add npm@10.9.0 latest
6. Trigger docs.npmjs.com update
gh workflow run update-cli.yml --repo npm/documentation
7. Merge release PR
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 v10.9.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:
Then, if we are opening a PR against the latest version of node:
gh workflow run create-node-pr.yml -f spec=next-10
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-10 -f branch=16
11. Label and fast-track nodejs/node PR
Note:
This requires being a nodejs collaborator. This could be you!
@npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output.
🚨🚨🚨
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
10.9.0
10.9.0 (2024-10-03)
Features
4d57928#7766 devEngines (feat: devEngines #7766) (@reggi)Bug Fixes
6ca609e#7789 ping and doctor commands fix for checking if registry is online (fix: never use cached npm ping request #7789) (@milaninfy)Documentation
63d6a73#7783 package.json: add brief section on exports, link to Node.js docs (docs(package.json): add brief section on exports, link to Node.js docs #7783) (@wheresrhys)366c07e#7776 remove incorrect note about npm install (docs: remove incorrect note about npm install #7776) (@wraithgar)Dependencies
60a7ee5#7803 hoist npm-normalize-package-bin20dd44f#7803 hoist minipass-fetch5795987#7803 updateproggy@3.0.099ccae3#7803 updatebin-links@5.0.075786ad#7803 update@npmcli/query@4.0.01c25a1d#7803 update@npmcli/node-gyp@4.0.02d7fc3d#7803 update@npmcli/name-from-folder@3.0.01e09334#7803 update@npmcli/metavuln-calculator@8.0.0820e983#7803 update@npmcli/installed-package-contents@3.0.09cd6603#7803 updateread-package-json-fast@4.0.0b84d907#7803 update@npmcli/git@6.0.153ed632#7803 updatewrite-file-atomic@6.0.0ab40dab#7803 updatewhich@5.0.0b1c4770#7803 updatevalidate-npm-package-name@6.0.08206c4f#7803 updatessri@12.0.08b7dbc8#7803 updateread@4.0.0f6909a0#7803 updateproc-log@5.0.0f9b2e18#7803 updateparse-conflict-json@4.0.0e7ab206#7803 updatepacote@19.0.0b28dbb1#7803 updatenpm-user-validate@3.0.0d13a20b#7803 updatenpm-registry-fetch@18.0.15208f74#7803 updatenpm-profile@11.0.1092f41f#7803 updatenpm-pick-manifest@10.0.050a7bc8#7803 updatenpm-package-arg@12.0.0591130d#7803 updatenpm-install-checks@7.1.0be6ae96#7803 updatenpm-audit-report@6.0.08d4060a#7803 updatenormalize-package-data@7.0.0105fa2b#7803 updatenopt@8.0.0eae4f57#7803 updatemake-fetch-happen@14.0.17214149#7803 updatejson-parse-even-better-errors@4.0.0c4bed31#7803 updateinit-package-json@7.0.1f54b155#7803 updateini@5.0.06deae9e#7803 updatehosted-git-info@8.0.0034c729#7803 updatecacache@19.0.1ddb8be0#7803 updateabbrev@3.0.0538a4cc#7803 update@npmcli/run-script@9.0.1b80d048#7803 update@npmcli/redact@3.0.081137fc#7803 update@npmcli/promise-spawn@8.0.12076368#7803 update@npmcli/package-json@6.0.1feac87c#7803 update@npmcli/map-workspaces@4.0.1dd90f9e#7803 update@npmcli/fs@4.0.0Chores
95e2cb1#7810 ignore .github folder in release-please (@reggi)be1e6da#7803 updateminify-registry-metadata@4.0.0(@reggi)43f2374#7803 updateignore-walk@7.0.0(@reggi)bb03036#7803 updatenpm-packlist@9.0.0(@reggi)2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)949d8f8#7803 engine ^18.17.0 || >=20.5.0 in package template (@reggi)fefd509#7764 deps: bump actions/download-artifact from 3 to 4 in /.github/workflows (chore(deps): bump actions/download-artifact from 3 to 4 in /.github/workflows #7764) (@dependabot[bot], @wraithgar)@npmcli/arborist@8.0.0@npmcli/config@9.0.0libnpmaccess@9.0.0libnpmdiff@7.0.0libnpmexec@9.0.0libnpmfund@6.0.0libnpmhook@11.0.0libnpmorg@7.0.0libnpmpack@8.0.0libnpmpublish@10.0.0libnpmsearch@8.0.0libnpmteam@7.0.0libnpmversion@7.0.0arborist: 8.0.0
8.0.0 (2024-10-03)
@npmcli/arboristnow supports node^18.17.0 || >=20.5.0Features
4d57928#7766 devEngines (feat: devEngines #7766) (@reggi)Bug Fixes
365580a#7803 align @npmcli/arborist to npm 10 node engine range (@reggi)Dependencies
5795987#7803 updateproggy@3.0.099ccae3#7803 updatebin-links@5.0.075786ad#7803 update@npmcli/query@4.0.01c25a1d#7803 update@npmcli/node-gyp@4.0.02d7fc3d#7803 update@npmcli/name-from-folder@3.0.01e09334#7803 update@npmcli/metavuln-calculator@8.0.0820e983#7803 update@npmcli/installed-package-contents@3.0.09cd6603#7803 updateread-package-json-fast@4.0.08206c4f#7803 updatessri@12.0.0f6909a0#7803 updateproc-log@5.0.0f9b2e18#7803 updateparse-conflict-json@4.0.0e7ab206#7803 updatepacote@19.0.0d13a20b#7803 updatenpm-registry-fetch@18.0.1092f41f#7803 updatenpm-pick-manifest@10.0.050a7bc8#7803 updatenpm-package-arg@12.0.0591130d#7803 updatenpm-install-checks@7.1.0105fa2b#7803 updatenopt@8.0.07214149#7803 updatejson-parse-even-better-errors@4.0.06deae9e#7803 updatehosted-git-info@8.0.0034c729#7803 updatecacache@19.0.1538a4cc#7803 update@npmcli/run-script@9.0.1b80d048#7803 update@npmcli/redact@3.0.02076368#7803 update@npmcli/package-json@6.0.1feac87c#7803 update@npmcli/map-workspaces@4.0.1dd90f9e#7803 update@npmcli/fs@4.0.0Chores
be1e6da#7803 updateminify-registry-metadata@4.0.0(@reggi)2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)config: 9.0.0
9.0.0 (2024-10-03)
@npmcli/confignow supports node^18.17.0 || >=20.5.0Bug Fixes
f846ad3#7803 align @npmcli/config to npm 10 node engine range (@reggi)Dependencies
f6909a0#7803 updateproc-log@5.0.0105fa2b#7803 updatenopt@8.0.0f54b155#7803 updateini@5.0.02076368#7803 update@npmcli/package-json@6.0.1feac87c#7803 update@npmcli/map-workspaces@4.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmaccess: 9.0.0
9.0.0 (2024-10-03)
libnpmaccessnow supports node^18.17.0 || >=20.5.0Bug Fixes
73068d6#7803 align libnpmaccess to npm 10 node engine range (@reggi)Dependencies
d13a20b#7803 updatenpm-registry-fetch@18.0.150a7bc8#7803 updatenpm-package-arg@12.0.0Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmdiff: 7.0.0
7.0.0 (2024-10-03)
libnpmdiffnow supports node^18.17.0 || >=20.5.0Bug Fixes
340a330#7803 align libnpmdiff to npm 10 node engine range (@reggi)Dependencies
820e983#7803 update@npmcli/installed-package-contents@3.0.0e7ab206#7803 updatepacote@19.0.050a7bc8#7803 updatenpm-package-arg@12.0.0Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)@npmcli/arborist@8.0.0libnpmexec: 9.0.0
9.0.0 (2024-10-03)
libnpmexecnow supports node^18.17.0 || >=20.5.0Bug Fixes
a2c8016#7803 align libnpmexec to npm 10 node engine range (@reggi)Dependencies
99ccae3#7803 updatebin-links@5.0.09cd6603#7803 updateread-package-json-fast@4.0.08b7dbc8#7803 updateread@4.0.0f6909a0#7803 updateproc-log@5.0.0e7ab206#7803 updatepacote@19.0.050a7bc8#7803 updatenpm-package-arg@12.0.0538a4cc#7803 update@npmcli/run-script@9.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)@npmcli/arborist@8.0.0libnpmfund: 6.0.0
6.0.0 (2024-10-03)
libnpmfundnow supports node^18.17.0 || >=20.5.0Bug Fixes
e7298de#7803 align libnpmfund to npm 10 node engine range (@reggi)Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)Dependencies
@npmcli/arborist@8.0.0libnpmhook: 11.0.0
11.0.0 (2024-10-03)
libnpmhooknow supports node^18.17.0 || >=20.5.0Bug Fixes
0e69c92#7803 align libnpmhook to npm 10 node engine range (@reggi)Dependencies
d13a20b#7803 updatenpm-registry-fetch@18.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmorg: 7.0.0
7.0.0 (2024-10-03)
libnpmorgnow supports node^18.17.0 || >=20.5.0Bug Fixes
47f6f76#7803 align libnpmorg to npm 10 node engine range (@reggi)Dependencies
d13a20b#7803 updatenpm-registry-fetch@18.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmpack: 8.0.0
8.0.0 (2024-10-03)
libnpmpacknow supports node^18.17.0 || >=20.5.0Bug Fixes
1b61379#7803 align libnpmpack to npm 10 node engine range (@reggi)Dependencies
e7ab206#7803 updatepacote@19.0.050a7bc8#7803 updatenpm-package-arg@12.0.0538a4cc#7803 update@npmcli/run-script@9.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)@npmcli/arborist@8.0.0libnpmpublish: 10.0.0
10.0.0 (2024-10-03)
libnpmpublishnow supports node^18.17.0 || >=20.5.0Bug Fixes
96f4e4e#7803 align libnpmpublish to npm 10 node engine range (@reggi)Dependencies
8206c4f#7803 updatessri@12.0.0f6909a0#7803 updateproc-log@5.0.0d13a20b#7803 updatenpm-registry-fetch@18.0.150a7bc8#7803 updatenpm-package-arg@12.0.08d4060a#7803 updatenormalize-package-data@7.0.0Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmsearch: 8.0.0
8.0.0 (2024-10-03)
libnpmsearchnow supports node^18.17.0 || >=20.5.0Bug Fixes
ecfa213#7803 align libnpmsearch to npm 10 node engine range (@reggi)Dependencies
d13a20b#7803 updatenpm-registry-fetch@18.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmteam: 7.0.0
7.0.0 (2024-10-03)
libnpmteamnow supports node^18.17.0 || >=20.5.0Bug Fixes
61d9a90#7803 align libnpmteam to npm 10 node engine range (@reggi)Dependencies
d13a20b#7803 updatenpm-registry-fetch@18.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)libnpmversion: 7.0.0
7.0.0 (2024-10-03)
libnpmversionnow supports node^18.17.0 || >=20.5.0Bug Fixes
d3c0b1e#7803 align libnpmversion to npm 10 node engine range (@reggi)Dependencies
b84d907#7803 update@npmcli/git@6.0.1f6909a0#7803 updateproc-log@5.0.07214149#7803 updatejson-parse-even-better-errors@4.0.0538a4cc#7803 update@npmcli/run-script@9.0.1Chores
2072705#7803 update@npmcli/eslint-config@5.0.1(@reggi)8035725#7756@npmcli/template-oss@4.23.3(@wraithgar)This PR was generated with Release Please. See documentation.