Commit 4ccffbe
committed
ci: drop unneeded npm@latest update step
The release workflow's first action installed npm@latest before running
semantic-release. The current latest npm (11.x) ships broken with a
MODULE_NOT_FOUND for promise-retry, which fails the entire release run.
Node 22's bundled npm (10.x) works fine with semantic-release, so this
upgrade step is unnecessary churn that exposes us to upstream npm bugs.
Removing it unblocks the SIT-163 release.1 parent 0c84eee commit 4ccffbe
1 file changed
Lines changed: 0 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
38 | 38 | | |
39 | 39 | | |
40 | 40 | | |
41 | | - | |
42 | | - | |
43 | | - | |
44 | 41 | | |
45 | 42 | | |
46 | 43 | | |
| |||
0 commit comments