From 71338badb858e10229fc4dd27db461f64883bc50 Mon Sep 17 00:00:00 2001 From: "seaturtle[bot]" Date: Thu, 23 Jul 2026 00:02:17 -0500 Subject: [PATCH] fix(cicd): pin npm@11 in publish workflow to unbreak npm oidc publish - the publish job upgrades npm to get oidc support (needs >= 11.5.1) when the runner's npm is older, via 'npm install -g npm@latest' - npm@latest rolled to 12.0.1, which requires node >= 22.22.2; .nvmrc pins 22.21.0, so the upgrade step EBADENGINE-failed before npm publish ran - this blocked the v1.8.0 publish (tag + gh release cut, but npm stayed 1.7.3) - pin to npm@11: still oidc-capable (>= 11.5.1) and compatible with node 22.21.0 .why = restore the npm publish path without a node bump; npm@latest tracking a node-incompatible major is the root cause, so pin to the compatible major Co-authored-by: ulad kasach --- .github/workflows/.publish-npm.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/.publish-npm.yml b/.github/workflows/.publish-npm.yml index 8321245..7808515 100644 --- a/.github/workflows/.publish-npm.yml +++ b/.github/workflows/.publish-npm.yml @@ -49,7 +49,7 @@ jobs: MIN_VERSION="11.5.1" if [ "$(printf '%s\n' "$MIN_VERSION" "$NPM_VERSION" | sort -V | head -n1)" != "$MIN_VERSION" ]; then echo "npm $NPM_VERSION < $MIN_VERSION, will upgrade npm now to support oidc..." - npm install -g npm@latest + npm install -g npm@11 # pin to 11.x: oidc-capable (>= 11.5.1) and compatible with the node pinned in .nvmrc; npm@latest (12.x) needs node >= 22.22.2 else echo "npm $NPM_VERSION >= $MIN_VERSION, ready to use!" fi