Skip to content

Commit a9dacef

Browse files
mishushakovclaude
andcommitted
Use Node 24 for release job instead of upgrading npm
Node 24.15 ships with npm 11.12, which already satisfies the OIDC publish requirement. Avoids the broken npm self-install in Node 22's tool cache (npm/cli#8859, "Cannot find module 'promise-retry'") by skipping the upgrade step entirely. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1 parent b412935 commit a9dacef

1 file changed

Lines changed: 2 additions & 7 deletions

File tree

.github/workflows/release.yml

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -331,10 +331,10 @@ jobs:
331331
with:
332332
version: 9.5
333333

334-
- name: Setup Node.js 22
334+
- name: Setup Node.js 24
335335
uses: actions/setup-node@v6
336336
with:
337-
node-version: "22.x"
337+
node-version: "24.x"
338338
registry-url: 'https://registry.npmjs.org'
339339
cache: pnpm
340340

@@ -343,11 +343,6 @@ jobs:
343343
pnpm config set auto-install-peers true
344344
pnpm config set exclude-links-from-lockfile true
345345
346-
- name: Update npm
347-
run: |
348-
npm install -g --force npm@^11.6
349-
npm --version
350-
351346
- name: Install dependencies
352347
run: pnpm install --frozen-lockfile
353348

0 commit comments

Comments
 (0)