Commit c4b3874
ci(publish): use NPM_TOKEN for the @next-alignment step (#377)
OIDC trusted publishing authorizes 'npm publish' but not 'npm dist-tag
add' — the dist-tag step runs as no-auth and silently fails with E401. The
release therefore lands with @latest=0.44.2 and @next stuck at the previous
version, breaking the documented '@next == @latest' invariant in CLAUDE.md.
Fix: pipe the legacy NPM_TOKEN (already in GitHub repo secrets, created
2026-02-21) through env on the dist-tag step ONLY. 'npm publish' still
uses OIDC. The token's dist-tag scope is the package (no IP allowlist
needed for that scope), and the workflow falls back gracefully if the
token is revoked/expired.
Verified by reading the script comment, the existing fallback path,
and the npm 'dist-tag' permission requirements.
Next release will auto-align @next. For 0.44.2 (this release), the
NPM_TOKEN secret may itself be stale — user must regenerate on npmjs.com
and re-add @next manually if needed.
Co-authored-by: open-swe[bot] <jonathan@jonathanborduas.com>1 parent d295ce4 commit c4b3874
1 file changed
Lines changed: 7 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
121 | 121 | | |
122 | 122 | | |
123 | 123 | | |
124 | | - | |
125 | | - | |
126 | | - | |
127 | | - | |
128 | | - | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
129 | 130 | | |
130 | 131 | | |
131 | 132 | | |
132 | 133 | | |
133 | | - | |
| 134 | + | |
134 | 135 | | |
135 | 136 | | |
136 | 137 | | |
| |||
0 commit comments