Skip to content

chore: release 10.9.3 #8385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 25, 2025
Merged

chore: release 10.9.3 #8385

merged 1 commit into from
Jun 25, 2025

Conversation

github-actions[bot]
Copy link
Contributor

🤖 I have created a release beep boop

10.9.3

10.9.3 (2025-06-25)

Bug Fixes

Dependencies

Chores

arborist: 8.0.1

8.0.1 (2025-06-25)

Bug Fixes

Chores

libnpmdiff: 7.0.1

Dependencies

libnpmexec: 9.0.1

Dependencies

libnpmfund: 6.0.1

Dependencies

libnpmpack: 8.0.1

Dependencies

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--release/v10 branch from ee363a1 to a4b6e57 Compare June 25, 2025 19:03
@github-actions github-actions bot requested a review from a team as a code owner June 25, 2025 19:03
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jun 25, 2025 •
edited by wraithgar
Loading

Release Manager

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

Release Checklist for v10.9.3

  • 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 8385 --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.3 locally

    npm i -g npm@10.9.3
    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 10 is not being set to latest.

    node . dist-tag add npm@10.9.3 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 release/v10
    git fetch
    git reset --hard origin/release/v10
    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 release/v10 -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.3 --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-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!

    • 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 github-actions bot force-pushed the release-please--branches--release/v10 branch from a4b6e57 to fcaf629 Compare June 25, 2025 19:03
@wraithgar wraithgar merged commit f69c403 into release/v10 Jun 25, 2025
22 checks passed
@wraithgar wraithgar deleted the release-please--branches--release/v10 branch June 25, 2025 20:25
@github-actions GitHub Actions
Copy link
Contributor Author

🤖 Created releases:

🌻

@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jun 25, 2025 •
edited
Loading

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.

🚨🚨🚨

@alexsch01
Copy link
Contributor

@wraithgar I assume this will eventually be a PR on nodejs side for 22

@wraithgar
Copy link
Member

We hope so @alexsch01. The script to make the PR is not currently working for backports and we're looking into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@wraithgar wraithgar wraithgar approved these changes

Assignees
No one assigned
Labels
autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@alexsch01 @wraithgar