pnpm stage
Added in: v11.3.0
Stages packages for publishing using npm's staged publishing workflow. Staged versions are not resolved by pnpm install until they are explicitly approved, letting you defer proof-of-presence (2FA) to a later point in time — useful for verifying release artifacts, smoke-testing CI, or coordinating multi-package releases.
pnpm stage <subcommand> [options]
Subcommands
publish
Stage a package for publishing.
pnpm stage publish [<tarball>|<dir>] [--tag <tag>] [--access <public|restricted>] [options]
Accepts the same arguments as pnpm publish, but uploads the tarball to staging instead of promoting it to the live registry. The resulting stage id is printed and can be used with the other subcommands.
Use --recursive (or -r) to stage every publishable package in the workspace.
list
List all staged package versions, or list the staged versions of a specific package.
pnpm stage list [<package-spec>]
view
Show details of a specific staged version.
pnpm stage view <stage-id>
approve
Approve a staged version, promoting it to the live registry. This is the step that consumes the one-time password.
pnpm stage approve <stage-id> [--otp <otp>]
reject
Reject a staged version and remove it from staging.
pnpm stage reject <stage-id> [--otp <otp>]
download
Download the tarball of a staged version for inspection.
pnpm stage download <stage-id>
Параметри
--registry <url>
The base URL of the npm registry. Стандартним значенням є типовий налаштований реєстр.
--tag <tag>
Registers the staged package with the given dist-tag. Defaults to latest.
--access <public|restricted>
Tells the registry whether the staged package should be public or restricted.
--json
Показати інформацію у форматі JSON. Applies to list, view, publish, and download.
--dry-run
Does everything stage publish would do except uploading to the registry.
--otp <otp>
One-time password for approve and reject.
--recursive, -r
Stage all publishable packages from the workspace.