Commit af2300d
fix(ci): unpin Node/npm engine mismatch breaking publish (#57)
`npm install -g npm@latest` began resolving to npm 12.0.1, whose engines
require Node ^22.22.2 || ^24.15.0 || >=26.0.0. The release workflow pins
Node 22.14.0, so the step failed with EBADENGINE and the v1.0.0 publish
never ran. Nothing in the repo changed -- npm 12 shipped and moved the
floor under a floating dist-tag.
Bump Node to 22.23.1 (current v22 LTS patch, satisfies ^22.22.2) and pin
npm to the major (npm@12) so the next npm major cannot silently break
releases again. The step exists only because Node 22 bundles npm 10.9.x,
which predates the OIDC trusted publishing support added in 11.5.1.
Node is bumped in ci.yml too, since CI and release are deliberately kept
on the same pin and drift between them is its own hazard.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent 61e35cb commit af2300d
2 files changed
Lines changed: 9 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
27 | 27 | | |
28 | 28 | | |
29 | 29 | | |
30 | | - | |
| 30 | + | |
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
| |||
56 | 56 | | |
57 | 57 | | |
58 | 58 | | |
59 | | - | |
| 59 | + | |
60 | 60 | | |
61 | 61 | | |
62 | 62 | | |
| |||
79 | 79 | | |
80 | 80 | | |
81 | 81 | | |
82 | | - | |
| 82 | + | |
83 | 83 | | |
84 | 84 | | |
85 | 85 | | |
| |||
105 | 105 | | |
106 | 106 | | |
107 | 107 | | |
108 | | - | |
| 108 | + | |
109 | 109 | | |
110 | 110 | | |
111 | 111 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
40 | 40 | | |
41 | 41 | | |
42 | 42 | | |
43 | | - | |
| 43 | + | |
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
47 | 47 | | |
48 | | - | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
49 | 52 | | |
50 | 53 | | |
51 | 54 | | |
| |||
0 commit comments