From e7f6a74fb569b73c61b6082da924a1193759e791 Mon Sep 17 00:00:00 2001 From: hiroTamada <88675973+hiroTamada@users.noreply.github.com> Date: Thu, 9 Jul 2026 15:54:39 +0000 Subject: [PATCH] ci: bump release Node to 24 so npm@latest installs npm@latest now resolves to npm@12, which dropped Node 20 support (requires ^22.22.2 || ^24.15.0 || >=26.0.0). The release job pinned Node 20, so `npm install -g npm@latest` failed with EBADENGINE and skipped GoReleaser. Node 24 is already the actions runtime and ships npm >= 11.5.1 for OIDC trusted publishing. Co-Authored-By: Claude Opus 4.8 --- .github/workflows/release.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml index 7861dc16..9b5da52d 100644 --- a/.github/workflows/release.yaml +++ b/.github/workflows/release.yaml @@ -35,7 +35,7 @@ jobs: - name: Set up Node.js uses: actions/setup-node@v6 with: - node-version: '20' + node-version: '24' registry-url: 'https://registry.npmjs.org' - name: Ensure latest npm (>= 11.5.1 for OIDC)