Skip to content

Skip already-published npm packages in release workflow - #1173

Open
JohnnyMorganz wants to merge 1 commit into
mainfrom
ci/npm-publish-skip-existing
Open

JohnnyMorganz wants to merge 1 commit into
mainfrom
ci/npm-publish-skip-existing

Conversation

@JohnnyMorganz

Copy link
Copy Markdown
Owner

The npm binary publish job loops over the platform packages and then publishes the main package. If one publish fails part-way (as happened for 2.6.0), re-running the job fails immediately on the packages that were already published.

This checks npm view <name>@<version> before each npm publish and skips versions that already exist, so a failed run can be re-run safely.

Note: not exercised end to end, since it only runs on a real release.

🤖 Generated with Claude Code

Allows re-running the npm binary publish job after a partial failure.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant