Skip to content

Split publish into separate PyPI and npm workflows#446

Merged
ndrezn merged 1 commit intomainfrom
split-npm-publish-workflow
Apr 3, 2026
Merged

Split publish into separate PyPI and npm workflows#446
ndrezn merged 1 commit intomainfrom
split-npm-publish-workflow

Conversation

@ndrezn
Copy link
Copy Markdown
Member

@ndrezn ndrezn commented Apr 3, 2026

Summary

  • Replaces publish.yml with two separate workflows:
    • pypi-publish.yml — publishes to PyPI on release
    • npm-publish.yml — publishes to npm on release, and supports manual trigger via workflow_dispatch
  • No dependencies between the two; they both only need the build job artifacts

Test plan

  • Verify workflow YAML is valid
  • Confirm npm environment exists in GitHub repo settings
  • Test with a release publish

🤖 Generated with Claude Code

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>
@ndrezn ndrezn requested a review from BSd3v April 3, 2026 13:53
Copy link
Copy Markdown
Collaborator

@BSd3v BSd3v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💃 LGTM, just moving the scripts essentially.


Failing tests are due to flakey that was fixed in other branches

@ndrezn ndrezn merged commit a48cfb0 into main Apr 3, 2026
0 of 3 checks passed
@ndrezn ndrezn deleted the split-npm-publish-workflow branch April 3, 2026 14:15
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.

2 participants