From a8a29c15890760dd584121f6b33d1ed844f87342 Mon Sep 17 00:00:00 2001 From: Brett Goss Date: Tue, 11 Aug 2026 17:58:04 +0000 Subject: [PATCH] fix(ci): publish on Node 24 npm 12 requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, so `npm install -g npm@latest` fails with EBADENGINE on the pinned Node 20. That has blocked every publish since 2026-07-13. Node 24 bundles npm 11.17.0, which already satisfies the npm >= 11.5.1 floor for trusted publishing, so the global npm install is no longer needed. --- .github/workflows/npm-publish.yml | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/.github/workflows/npm-publish.yml b/.github/workflows/npm-publish.yml index 5ad0d19ab..e872bf5b9 100644 --- a/.github/workflows/npm-publish.yml +++ b/.github/workflows/npm-publish.yml @@ -22,10 +22,12 @@ jobs: steps: - uses: actions/checkout@v4 + # Node 24 bundles npm 11.17.0, satisfying the npm >= 11.5.1 requirement + # for trusted publishing. - name: Setup node uses: actions/setup-node@v4 with: - node-version: 20 + node-version: 24 registry-url: "https://registry.npmjs.org" - run: | @@ -36,9 +38,5 @@ jobs: pnpm --version pnpm i - # Ensure npm 11.5.1 or later is installed - - name: Update npm - run: npm install -g npm@latest - - name: Publish to npm run: pnpm publish -r --access public