ci: remove standalone release-npm.yml workflow#947
Conversation
The release-npm job in release.yml already handles npm publishing as part of every normal release. The standalone workflow was an emergency fallback that is no longer needed now that the job lives in release.yml. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
📦 TestPyPI package publishedpip install --index-strategy unsafe-best-match --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ buckaroo==0.15.3.dev28250457457or with uv: uv pip install --index-strategy unsafe-best-match --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ buckaroo==0.15.3.dev28250457457MCP server for Claude Codeclaude mcp add buckaroo-table -- uvx --from "buckaroo[mcp]==0.15.3.dev28250457457" --index-strategy unsafe-best-match --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ buckaroo-table📖 Docs preview🎨 Storybook preview |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cbae97a305
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # Use this workflow only when you need to re-publish a specific version | ||
| # without triggering a full PyPI release (e.g. after a Trusted Publisher | ||
| # config fix or a transient npm outage). |
There was a problem hiding this comment.
When npm publishing needs to be retried for an already-created Python release (the Trusted Publisher config-fix or npm-outage case documented here), deleting this workflow leaves no new manual dispatch path that accepts the existing version: the remaining release.yml workflow only accepts a bump input and its npm job publishes needs.release.outputs.version, so dispatching it would move to the next semver release instead of publishing the missing buckaroo-js-core@<existing>. Please keep a standalone/manual npm publish path or add an npm-only version input before removing this fallback.
Useful? React with 👍 / 👎.
1 participant
The
release-npmjob inrelease.ymlhandles npm publishing as part of every normal release. The standalonerelease-npm.ymlwas an emergency fallback introduced before that job existed, and is now redundant.🤖 Generated with Claude Code