CLI documentation update from CI
npm CLI robot committed
Jun 2, 2026 at 03:25 UTC
3de468a6bcf68dbd839aeeb30536ab4ef1192885
2 files changed
+15
-15
cli-cache.json
+1
-1
@@ -2,5 +2,5 @@
2
"v8": "aa8fff11cdab94fff1a2160ee5241f5f4632e96b",
3
"v9": "64763a341e7aa5b456e696f956759bf9b3440dc1",
4
"v10": "189ba136a75c773927a5cb8922e6b00c71814d35",
5
- "v11": "b97edc0193017800ecb1f26d212977729ca19739"
5
+ "v11": "9f3c97f83443ee00b9ca6beaf3e8cec95d3199ad"
6
}
\ No newline at end of file
content/cli/v11/commands/npm-stage.mdx
+14
-14
@@ -77,14 +77,14 @@ Before using `npm stage` commands, ensure the following requirements are met:
77
78
### 2FA Requirements by Subcommand
79
80
-| Command | Requires 2FA | Notes |
81
-| -------------------- | ------------ | -------------------------------------------------------- |
82
-| `npm stage publish` | No | Designed for automated workflows; defers 2FA to approval |
83
-| `npm stage list` | No | View staged packages |
84
-| `npm stage view` | No | View staged package details |
85
-| `npm stage approve` | Yes | Prompts for 2FA to publish the staged package |
86
-| `npm stage reject` | Yes | Prompts for 2FA to permanently remove the staged package |
87
-| `npm stage download` | No | Downloads the tarball for local inspection |
80
+| Command | Requires 2FA | Notes |
81
+| --- | --- | --- |
82
+| `npm stage publish` | No | Designed for automated workflows; defers 2FA to approval |
83
+| `npm stage list` | No | View staged packages |
84
+| `npm stage view` | No | View staged package details |
85
+| `npm stage approve` | Yes | Prompts for 2FA to publish the staged package |
86
+| `npm stage reject` | Yes | Prompts for 2FA to permanently remove the staged package |
87
+| `npm stage download` | No | Downloads the tarball for local inspection |
88
89
### Tag Behavior
90
@@ -96,12 +96,12 @@ The tag is an immutable property of the staged package. Once a package is staged
96
97
The key difference with staged publishing is that `npm stage publish` never requires a 2FA prompt, regardless of token type. This is what makes it suitable for automated workflows. The goal of `npm stage publish` is deferring proof-of-presence to a later point in time.
98
99
-| Token Type | `npm stage publish` | `npm publish` |
100
-| ------------------ | ---------------------- | ----------------------------------------------------- |
101
-| GAT with bypass | Can stage | Can publish (if allowed by package publishing access) |
102
-| GAT without bypass | Can stage | 2FA prompt (if allowed by package publishing access) |
103
-| Session token | Can stage | 2FA prompt |
104
-| Trust token (OIDC) | Can stage (if allowed) | Can publish (if allowed) |
99
+| Token Type | `npm stage publish` | `npm publish` |
100
+| --- | --- | --- |
101
+| GAT with bypass | Can stage | Can publish (if allowed by package publishing access) |
102
+| GAT without bypass | Can stage | 2FA prompt (if allowed by package publishing access) |
103
+| Session token | Can stage | 2FA prompt |
104
+| Trust token (OIDC) | Can stage (if allowed) | Can publish (if allowed) |
105
106
### Trust Relationship Permissions
107