fix: tolerate already-published npm packages in release workflow (#61)

When a release run partially succeeds (some platform packages publish
but a later one fails), re-running the workflow would fail immediately
on the first already-published package. Now checks if the version is
already on the registry and skips it instead of failing.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Wenxin-Jiang

.github/workflows/release.yml

@@ -294,7 +294,13 @@ jobs:
         run: |
           for pkg_dir in npm/socket-patch-*/; do
             echo "Publishing ${pkg_dir}..."
-            npm publish "./${pkg_dir}" --provenance --access public
+            npm publish "./${pkg_dir}" --provenance --access public || {
+              if npm view "@socketsecurity/$(basename "$pkg_dir")@${{ needs.version.outputs.version }}" version >/dev/null 2>&1; then
+                echo "Already published, skipping."
+              else
+                exit 1
+              fi
+            }
           done
 
       - name: Wait for npm registry propagation
@@ -304,7 +310,14 @@ jobs:
         run: cp README.md npm/socket-patch/README.md
 
       - name: Publish main package
-        run: npm publish ./npm/socket-patch --provenance --access public
+        run: |
+          npm publish ./npm/socket-patch --provenance --access public || {
+            if npm view "@socketsecurity/socket-patch@${{ needs.version.outputs.version }}" version >/dev/null 2>&1; then
+              echo "Already published, skipping."
+            else
+              exit 1
+            fi
+          }
 
   pypi-publish:
     needs: [version, build]