GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — fix: tolerate already-published npm packages in release workflow by Wenxin-Jiang · Pull Request #61 · SocketDev/socket-patch

Conversation

@Wenxin-Jiang

@Wenxin-Jiang Wenxin Jiang (Wenxin-Jiang) commented Apr 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Makes the npm publish loop idempotent — if a platform package is already published, it skips instead of failing
  • Same treatment for the main @socketsecurity/socket-patch package
  • Fixes the issue where a partial release failure (e.g. v2.1.3 where some packages published before the Sigstore 409) makes re-running the workflow impossible

Context

The v2.1.3 release partially published some npm platform packages before failing on socket-patch-linux-x64-musl (Sigstore transparency log conflict). Re-running the workflow then fails immediately on the first already-published package because set -e aborts the script.

Test plan

  • Merge and re-trigger the Release workflow for v2.1.3
  • Verify already-published packages are skipped and remaining ones publish successfully

🤖 Generated with Claude Code

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@Wenxin-Jiang @claude
fix: tolerate already-published npm packages in release workflow
a87e11d
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) <[email protected]>
mikolalysenko
Mikola Lysenko (mikolalysenko) approved these changes Apr 9, 2026
View reviewed changes
@Wenxin-Jiang
Wenxin Jiang (Wenxin-Jiang) merged commit 70710b1 into main Apr 9, 2026
19 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@Wenxin-Jiang
Wenxin Jiang (Wenxin-Jiang) deleted the fix/npm-publish-idempotent branch April 9, 2026 13:39
@Wenxin-Jiang Wenxin Jiang (Wenxin-Jiang) mentioned this pull request Apr 9, 2026
v2.1.4: bump and sync package versions #62
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mikolalysenko Mikola Lysenko (mikolalysenko) mikolalysenko approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@Wenxin-Jiang @mikolalysenko
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.