From 6bb498b82feb52f74c6f8c69dd370357ffdd7b08 Mon Sep 17 00:00:00 2001 From: David Antoon Date: Mon, 5 Oct 2026 17:20:48 +0300 Subject: [PATCH] ci: pin npm to 11.5.1 in the publish workflow npm@latest is now npm 12, which requires Node ^22.22.2, ^24.15.0 or >=26, while .nvmrc pins Node 24.11, so the Update npm CLI step failed with EBADENGINE before anything was published. 11.5.1 is the first npm with OIDC trusted publishing and supports Node 24.11; agentfront/frontmcp pins the same version. --- .github/workflows/publish-release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/publish-release.yml b/.github/workflows/publish-release.yml index ea32884..d7e724c 100644 --- a/.github/workflows/publish-release.yml +++ b/.github/workflows/publish-release.yml @@ -74,7 +74,7 @@ jobs: registry-url: "https://registry.npmjs.org/" - name: Update npm CLI for trusted publishing - run: npm install -g npm@latest + run: npm install -g npm@11.5.1 # Pinned: the first npm with OIDC publishing; npm@latest can require a newer Node than .nvmrc - name: Compute version id: version