Skip to content

chore: release 11.6.3 #8671

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
owlstronaut merged 1 commit into from
Nov 19, 2025
Merged

chore: release 11.6.3 #8671

owlstronaut merged 1 commit into from
Nov 19, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 13, 2025 •
edited
Loading

🤖 I have created a release beep boop

11.6.3

11.6.3 (2025-11-19)

Bug Fixes

Documentation

Dependencies

Chores

arborist: 9.1.7

9.1.7 (2025-11-19)

Bug Fixes

Dependencies

config: 10.4.3

10.4.3 (2025-11-19)

Bug Fixes

Dependencies

libnpmdiff: 8.0.10

Dependencies

libnpmexec: 10.1.9

10.1.9 (2025-11-19)

Bug Fixes

Dependencies

libnpmfund: 7.0.10

Dependencies

libnpmpack: 9.0.10

Dependencies

libnpmpublish: 11.1.3

11.1.3 (2025-11-19)

Dependencies

libnpmversion: 8.0.3

8.0.3 (2025-11-19)

Dependencies

Chores

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner October 13, 2025 15:59
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 13, 2025 •
edited
Loading

Release Manager

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

Release Checklist for v11.6.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 8671 --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.6.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-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 github-actions bot force-pushed the release-please--branches--latest branch 11 times, most recently from 60466ce to 0b29a15 Compare October 20, 2025 15:46
@AviVahl
Copy link

AviVahl commented Oct 28, 2025

@wraithgar

Considering v11.6.2 changes every lock file out there by shuffling around bunch of "peer": true, and this release includes #8645, which reverts that behavior, shouldn't this be released with more haste?

One may also want to take into account that Node 24 is about to go LTS and include that lockfile disrupting npm release.

Been following this PR and I can't understand why this has not landed and released to the wild. Any chance you could clarify? Are there other regressions involved?

@Artur-
Copy link
Contributor

Artur- commented Oct 28, 2025

In my opinion, #8689 also needs to be resolved before this npm release becomes part of Node 24 LTS. Currently commands like npm ls produce errors in valid projects.

Not saying that it blocks a 11.6.3 releases but it is very much needed.

@liamcmitchell liamcmitchell mentioned this pull request Oct 29, 2025
Closed
2 tasks
@JRaspass JRaspass mentioned this pull request Nov 3, 2025
Open
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 2 times, most recently from 39d1740 to 9604f6f Compare November 3, 2025 21:08
@trentm trentm mentioned this pull request Nov 5, 2025
Merged
@jeremiewtd
Copy link

jeremiewtd commented Nov 12, 2025

Hi,
Any news on this release? Most people have been waiting for the lock file bug to be fixed for almost a month.

@github-actions github-actions bot force-pushed the release-please--branches--latest branch 8 times, most recently from 182f418 to ba2bddf Compare November 18, 2025 17:59
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 4 times, most recently from 11336a6 to 0c0a996 Compare November 18, 2025 22:50
@MikeMcC399 MikeMcC399 mentioned this pull request Nov 19, 2025
Open
@github-actions github-actions bot force-pushed the release-please--branches--latest branch 5 times, most recently from 6d2f548 to eea86c5 Compare November 19, 2025 18:29
@github-actions github-actions bot force-pushed the release-please--branches--latest branch from eea86c5 to 7b6cc82 Compare November 19, 2025 18:30
@owlstronaut owlstronaut merged commit 7da8fdd into latest Nov 19, 2025
22 checks passed
@owlstronaut owlstronaut deleted the release-please--branches--latest branch November 19, 2025 20:54
@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 19, 2025

🤖 Created releases:

🌻

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 19, 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.

🚨🚨🚨

@d0sboots d0sboots mentioned this pull request Nov 28, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@owlstronaut owlstronaut owlstronaut 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.

4 participants

@AviVahl @Artur- @jeremiewtd @owlstronaut