From c91ced9523dd99f2082feb868111b2644c0f45a9 Mon Sep 17 00:00:00 2001 From: Arun Sharma Date: Thu, 9 Jul 2026 18:25:49 -0700 Subject: [PATCH] Pin npm upgrade to v11 instead of latest npm@latest now resolves to version 12.0.0 (released 2026-07-08) which breaks 'npm publish --provenance' with MODULE_NOT_FOUND for 'sigstore'. Pin to npm@11 (the previous latest, currently 11.18.0) which was verified working in CI run #649. The upgrade step is kept because the bundled npm 10.9.x in Node 22 was historically insufficient for trusted publishing support. --- .github/workflows/build-and-deploy.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/build-and-deploy.yml b/.github/workflows/build-and-deploy.yml index 3b0ac43a3..72ace6eb2 100644 --- a/.github/workflows/build-and-deploy.yml +++ b/.github/workflows/build-and-deploy.yml @@ -419,6 +419,9 @@ jobs: node-version: "22" registry-url: "https://registry.npmjs.org" + - name: Upgrade npm + run: npm install -g npm@11 + - name: Package Node.js API (main + per-platform sub-packages) run: node package working-directory: tools/nodejs_api @@ -521,6 +524,9 @@ jobs: node-version: "20" registry-url: "https://registry.npmjs.org" + - name: Upgrade npm + run: npm install -g npm@11 + - name: Show tarball contents run: tar -tvf lbug-wasm.tar.gz working-directory: tools/wasm