Harden npm publish to tolerate individual platform failures

A single platform package hitting the npm spam filter was preventing the
shim package from being published. The loop now continues on failure and
reports warnings instead of aborting.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: m2de

.github/workflows/release.yml

@@ -171,13 +171,21 @@ jobs:
             "getapi-cli-win32-x64"
           )
 
+          failed=""
           for pkg in "${PLATFORMS[@]}"; do
             echo "Publishing ${pkg}..."
             cd "npm/${pkg}"
-            npm publish --access public
+            if ! npm publish --access public; then
+              echo "::warning::Failed to publish ${pkg}"
+              failed="${failed} ${pkg}"
+            fi
             cd ../..
           done
 
+          if [ -n "$failed" ]; then
+            echo "::warning::Some platform packages failed to publish:${failed}"
+          fi
+
       - name: Publish shim package
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}