From 5f3c228609f30e4b9d14dca9a2375edf696a1ea0 Mon Sep 17 00:00:00 2001 From: bilby91 <2201079+bilby91@users.noreply.github.com> Date: Tue, 18 Aug 2026 12:47:35 +0000 Subject: [PATCH] ci: run the publish job on Node 24 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The publish job pinned Node 20 and then ran `npm install -g npm@latest` to get a version new enough for trusted publishing. npm 12 requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, so that step now fails with EBADENGINE and no publish can complete — including the prerelease chained off a green CI run on main. Move the pin to Node 24, which npm@latest supports. Co-Authored-By: Claude Opus 5 --- .github/workflows/publish.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index e4ac59ff..e26054c3 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -63,7 +63,10 @@ jobs: - name: Setup Node.js for npm uses: actions/setup-node@v4 with: - node-version: '20' + # Must stay within npm@latest's supported range: npm 12 requires + # ^22.22.2 || ^24.15.0 || >=26.0.0, so the previous '20' pin made the + # `npm install -g npm@latest` step below fail with EBADENGINE. + node-version: '24' registry-url: 'https://registry.npmjs.org' # Ensure npm 11.5.1 or later for trusted publishing