From 38e639f4d88ed4a92ed5043d87a63533736864dd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Yusuf=20To=CC=88r?=
 <3296904+yusuftor@users.noreply.github.com>
Date: Tue, 3 Nov 2026 14:21:16 +0100
Subject: [PATCH] Pin npm 11 for trusted publishing on Node 20

npm 12 refuses to install on Node 20, so the 1.0.17 publish failed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 .github/workflows/build-test-publish-superscript-npm.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/build-test-publish-superscript-npm.yml b/.github/workflows/build-test-publish-superscript-npm.yml
index 4cdce68..fbf234d 100644
--- a/.github/workflows/build-test-publish-superscript-npm.yml
+++ b/.github/workflows/build-test-publish-superscript-npm.yml
@@ -159,8 +159,8 @@ jobs:
       - name: Publish to NPM
         if: github.event_name == 'push' && github.ref == 'refs/heads/master'
         run: |
-          # Trusted publishing needs npm 11.5.1 or later.
-          npm install -g npm@latest
+          # Trusted publishing needs npm 11.5.1 or later; npm 12 needs Node 22+.
+          npm install -g npm@^11.5.1
           cd wasm
           # Try a normal publish first; if it fails (e.g. first-time publish of a
           # scoped package), retry with --access public.