Commit 0f5b084
ci: drop
Run 24361722242 (v0.2.0 release) failed at the "Install latest npm"
step with a MODULE_NOT_FOUND error for `promise-retry` inside
@npmcli/arborist/lib/arborist/rebuild.js. Same bug hits main
codeceptjs/publish-beta.yml on the same Node 22.22.2 runner
(run 24115715943, 4.0.0-rc.12).
Root cause: a regression in how `npm install -g npm@latest` re-enters
arborist when the user's local project already has node_modules. The
step is cosmetic for us — Node 22 bundles npm 10.9+, and --provenance
has shipped since npm 9.5, so there's no functional reason to force a
global reinstall on every publish.
Fix: remove the step. If a future feature ever needs a newer npm,
pin to a specific known-good version (e.g. npm@11) rather than @latest.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>npm install -g npm@latest — fails under Node 22.22+1 parent 3f135b9 commit 0f5b084
1 file changed
Lines changed: 6 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
39 | 39 | | |
40 | 40 | | |
41 | 41 | | |
42 | | - | |
43 | | - | |
44 | | - | |
45 | | - | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
46 | 47 | | |
47 | 48 | | |
48 | 49 | | |
| |||
69 | 70 | | |
70 | 71 | | |
71 | 72 | | |
72 | | - | |
| 73 | + | |
73 | 74 | | |
74 | 75 | | |
75 | 76 | | |
| |||
0 commit comments