Avoid npm@12 while sigstore bug persists (#4169)

Issue: npm/cli#9722

Author: ddbeck

.github/workflows/publish_next_compute-baseline.yml

@@ -51,9 +51,11 @@ jobs:
       # A two-step install is required to work around a bad `npm` version that
       # comes bundled with Node 22.22.
       # See https://github.com/npm/cli/issues/9151#issuecomment-4129185112
+      # And we can't yet use npm@12 due to a bug:
+      # See https://github.com/npm/cli/issues/9722
       - run: |
           npm install -g 'npm@10'
-          npm install -g 'npm@>=11.5.1'  # required for trusted publishing
+          npm install -g 'npm@^11.5.1'  # required for trusted publishing
 
       - run: npm ci
       - name: Get package.json version

.github/workflows/publish_next_web-features.yml

@@ -59,9 +59,11 @@ jobs:
       # A two-step install is required to work around a bad `npm` version that
       # comes bundled with Node 22.22.
       # See https://github.com/npm/cli/issues/9151#issuecomment-4129185112
+      # And we can't yet use npm@12 due to a bug:
+      # See https://github.com/npm/cli/issues/9722
       - run: |
           npm install -g 'npm@10'
-          npm install -g 'npm@>=11.5.1'  # required for trusted publishing
+          npm install -g 'npm@^11.5.1'  # required for trusted publishing
       - run: npm ci
 
       - run: npm run build