Skip to content

chore: release 12.0.0-pre.1 - #9387

Merged
owlstronaut merged 1 commit into
latestfrom
release-please--branches--latest
Jun 19, 2026
Merged

chore: release 12.0.0-pre.1#9387
owlstronaut merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actions github-actions Bot commented May 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

12.0.0-pre.1

12.0.0-pre.1 (2026-06-19)

⚠️ BREAKING CHANGES

  • Preserve https protocol when working with git (fix!: Preserve https protocol when working with git #8703)
  • The default license for npm init has been changed from "ISC" to an empty string. If not set, the license field will be omitted from new packages.
  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.
  • root `preinstall` now runs before dependencies are installed.
  • unknown configs in .npmrc, unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning.

Features

Bug Fixes

Documentation

Dependencies

Chores

arborist: 10.0.0-pre.1

10.0.0-pre.1 (2026-06-19)

⚠️ BREAKING CHANGES

Features

Bug Fixes

Dependencies

Chores

config: 11.0.0-pre.1

11.0.0-pre.1 (2026-06-19)

⚠️ BREAKING CHANGES

  • The default license for npm init has been changed from "ISC" to an empty string. If not set, the license field will be omitted from new packages.
  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.
  • unknown configs in .npmrc, unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning.

Features

Bug Fixes

Dependencies

Chores

libnpmaccess: 11.0.0-pre.0

11.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Dependencies

Chores

libnpmdiff: 9.0.0-pre.0

9.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.

Features

Bug Fixes

Dependencies

Chores

libnpmexec: 11.0.0-pre.0

11.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Bug Fixes

Dependencies

Chores

libnpmfund: 8.0.0-pre.0

8.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Bug Fixes

Chores

Dependencies

libnpmorg: 9.0.0-pre.0

9.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Dependencies

Chores

libnpmpack: 10.0.0-pre.1

10.0.0-pre.1 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.

Features

Bug Fixes

Dependencies

Chores

libnpmpublish: 12.0.0-pre.0

12.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • opts.access now defaults to null instead of 'public'. With null, libnpmpublish no longer sets an explicit access level in the publish payload, so new scoped packages are created as restricted (registry default) and republishes preserve the existing access level. Callers that want to force public access must now pass access: 'public' explicitly.

Features

Bug Fixes

Dependencies

Chores

libnpmsearch: 10.0.0-pre.0

10.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Dependencies

Chores

libnpmteam: 9.0.0-pre.0

9.0.0-pre.0 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Dependencies

Chores

libnpmversion: 9.0.0-pre.1

9.0.0-pre.1 (2026-06-19)

⚠️ BREAKING CHANGES

  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

Features

Bug Fixes

Documentation

Dependencies

Chores

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot requested review from a team as code owners May 21, 2026 15:52
@github-actions

github-actions Bot commented May 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Release Manager

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

Release Checklist for v12.0.0-pre.1

  • 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 9387 --force
    npm run resetdeps
    node scripts/git-dirty.js

  • 2. Check CI status

    gh pr checks --watch

  • 3. Log in to npm

    npm login sessions are short lived, so you will want to have a fresh one before you publish.

    npm login

  • 4. 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-12.

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

    node scripts/publish.js --test

  • 5. Optionally install and test npm@12.0.0-pre.1 locally

    npm i -g npm@12.0.0-pre.1
    npm --version
npm whoami
npm help install
# etc

  • 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 v12.0.0-pre.1 --latest

  • 10. Open nodejs/node PR to update npm

    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.

    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 -R npm/cli -f spec=next-12

    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.

    For example, this will create a PR on nodejs/node to the v16.x-staging branch:

    gh workflow run create-node-pr.yml -R npm/cli -f spec=next-12 -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
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included

@github-actions
github-actions Bot force-pushed the release-please--branches--latest branch 24 times, most recently from aae5900 to 56bee35 Compare May 27, 2026 19:44
This was referenced May 27, 2026
Open
Merged
@github-actions
github-actions Bot force-pushed the release-please--branches--latest branch 24 times, most recently from 677dacd to a5df59c Compare June 3, 2026 21:42
@JamieMagee JamieMagee mentioned this pull request Jun 11, 2026
Closed
@manzoorwanijk manzoorwanijk mentioned this pull request Jun 19, 2026
Open
@github-actions

github-actions Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions

github-actions Bot commented Jun 19, 2026 •
edited
Loading