You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: prevent inline code from wrapping in table cells (#1968)
## Problem
Inline code elements (e.g. `--provenance`, `--dry-run`) inside table
cells can break across lines, making flag names hard to read.
## Fix
Adds `white-space: nowrap` to `code` elements inside `td` and `th` in
the `Table` styled component.
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|`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
88
89
89
### Tag Behavior
90
90
@@ -96,12 +96,12 @@ The tag is an immutable property of the staged package. Once a package is staged
96
96
97
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
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) |
0 commit comments