Repository navigation
Commit 8cd793c
authored
fix: activate pinned npm via corepack in publish workflow (#48)
The publish workflow has been silently failing since v0.3.1 with
MODULE_NOT_FOUND: promise-retry during `npm install -g npm@latest`.
Root cause: the self-upgrade path on the runner's prebuilt npm tree
leaves @npmcli/arborist's dependency graph half-replaced.
Discovered while releasing v0.3.2 — both v0.3.1 and v0.3.2 tags exist
on GitHub but neither version is actually on npm; `npm view @aictrl/cli
versions` tops out at 0.3.0. This is why the optionalDependencies fix
from #46 hadn't reached users.
Switch to `corepack prepare [email protected] --activate`: corepack installs
to its own shim directory and never touches the bundled npm tree, so
the self-upgrade corruption path is unreachable. Pinning to 11.5.2
(minimum OIDC trusted publishing support + 2 patch releases) instead
of tracking a moving `@latest` target.1 parent 02d828f commit 8cd793c
1 file changed
Lines changed: 15 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
25 | | - | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
26 | 39 | | |
27 | 40 | | |
28 | 41 | | |
| |||
0 commit comments