Repository navigation
Commit c0b65ad
fix: pin publish workflow npm to 11.10.1 (pre promise-retry removal)
#48's corepack approach didn't actually activate: `npm --version` after
`corepack prepare [email protected] --activate` reported 10.9.7 (the runner's
bundled npm), not 11.5.2. With only 10.9.x on PATH, OIDC trusted
publishing never engaged and every publish in the workflow failed with
ENEEDAUTH — the final `Publish @aictrl/cli` step surfaced the failure
because it was the only one without `|| true` masking.
Root cause of the original `npm install -g npm@latest` corruption: in
npm 11.11.0 (npm/cli#9008) the `promise-retry` dep was replaced with
`@gar/promise-retry`. Installing >=11.11.0 over the runner's bundled
10.9.x tree leaves orphan arborist files still `require('promise-retry')`
and crashes on first invocation. v0.3.0 (March 27) worked because the
runner's bundled npm was 10.9.4 on that image — just different enough
from 10.9.3 / 10.9.7 to not produce the orphan. Pure coincidence.
Pinning to 11.10.1 (last release before the promise-retry removal)
avoids the boundary entirely, stays ≥11.5.0 for OIDC trusted publishing
support, and uses the same `npm install -g` mechanism that v0.3.0
proved works with auto-OIDC auth.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>1 parent 8cd793c commit c0b65ad
1 file changed
Lines changed: 16 additions & 12 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
30 | 28 | | |
31 | | - | |
32 | | - | |
33 | | - | |
34 | | - | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
35 | 40 | | |
36 | | - | |
37 | | - | |
| 41 | + | |
38 | 42 | | |
39 | 43 | | |
40 | 44 | | |
| |||
0 commit comments