chore(sdk): bump Python + TS SDK versions to 0.5.1 — unblock PyPI publish#229
Merged
Conversation
v0.5.0 and v0.5.1 PyPI publishes both failed because the workspace
Cargo.toml version was bumped (0.3.4 → 0.5.0 → 0.5.1) without
matching bumps to the SDK manifests:
v0.5.0 publish-pypi run 26964456868: failure ("SDK version 0.3.4 != release tag 0.5.0")
v0.5.1 publish-pypi run 26993769469: failure ("SDK version 0.3.4 != release tag 0.5.1")
v0.5.1 manual dispatch 26993790763: failure (same — workflow_dispatch
skips the check but the
resulting sdist still
has version 0.3.4 which
already exists on PyPI)
Bumps now in lockstep with the v0.5.1 GitHub Release:
sdk/python/pyproject.toml 0.3.4 → 0.5.1
sdk/python/forkd/__init__.py 0.3.4 → 0.5.1
sdk/typescript/package.json 0.3.4 → 0.5.1
After merge, manually dispatch publish-pypi.yml to fix PyPI. NPM
needs a separate ts-v0.5.1 tag push (publish-npm only fires on
that prefix) — out of scope here; can be done as a follow-up.
NOT bumped:
sdk/mcp/pyproject.toml stays at 0.2.0 — has its own tag prefix
(mcp-v*) and publish workflow (publish-pypi-mcp.yml). Its lifecycle
is independent of the forkd Rust release cadence.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
v0.5.0 and v0.5.1 PyPI publishes both failed because the workspace `Cargo.toml` version bumped (0.3.4 → 0.5.0 → 0.5.1) without matching SDK manifest updates. PyPI is still showing 0.3.4 as latest `forkd`.
Three failed runs:
Bumps
Not bumped
`sdk/mcp/pyproject.toml` stays at 0.2.0 — has its own tag prefix (`mcp-v*`) and its own publish workflow (`publish-pypi-mcp.yml`). Independent lifecycle.
Post-merge
Manually dispatch `publish-pypi.yml` on main to publish 0.5.1 to PyPI. NPM publish needs a separate `ts-v0.5.1` tag push (`publish-npm.yml` only fires on that prefix) — can be follow-up.
Test plan
🤖 Generated with Claude Code