Split publish into separate PyPI and npm workflows#446
Merged
Conversation
Replaces the single publish.yml with: - pypi-publish.yml: publishes to PyPI on release - npm-publish.yml: publishes to npm on release + supports manual trigger via workflow_dispatch Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
BSd3v
approved these changes
Apr 3, 2026
Collaborator
BSd3v
left a comment
There was a problem hiding this comment.
💃 LGTM, just moving the scripts essentially.
Failing tests are due to flakey that was fixed in other branches
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
publish.ymlwith two separate workflows:pypi-publish.yml— publishes to PyPI on releasenpm-publish.yml— publishes to npm on release, and supports manual trigger viaworkflow_dispatchbuildjob artifactsTest plan
npmenvironment exists in GitHub repo settings🤖 Generated with Claude Code