Skip to content

Bump to 0.5.1 (0.5.0 burned by stale TS release)#25

Merged
mgoldsborough merged 1 commit into
mainfrom
bump-0.5.1
Apr 16, 2026
Merged

Bump to 0.5.1 (0.5.0 burned by stale TS release)#25
mgoldsborough merged 1 commit into
mainfrom
bump-0.5.1

Conversation

@mgoldsborough
Copy link
Copy Markdown
Contributor

Summary

Bumps both SDKs to 0.5.1. The 0.5.0 version number is unusable: upjack@0.5.0 was published to npm from a stale TypeScript commit that bumped the version without applying the flat-kwarg contract change described in PR #22. To keep the "same version = same contract across SDKs" invariant promised in the CHANGELOG, we skip 0.5.0 and release the corrected code as 0.5.1.

Files changed

  • lib/python/pyproject.toml → 0.5.1
  • lib/python/src/upjack/__init__.py → 0.5.1
  • lib/python/uv.lock (regenerated)
  • lib/typescript/package.json → 0.5.1
  • CHANGELOG.md — header renamed to 0.5.1 with a note on the version skip

Test plan

  • make -C lib/python check — 411 tests pass
  • cd lib/typescript && npm test — 282 tests pass
  • After merge: tag python-v0.5.1 + typescript-v0.5.1 to trigger PyPI + npm publish
  • npm deprecate upjack@0.5.0 "published without the flat-kwarg contract change; please upgrade to 0.5.1"

Related

An earlier commit bumped lib/typescript/package.json to 0.5.0 without
applying the flat-kwarg contract change. The resulting npm `upjack@0.5.0`
shipped the old {data: {...}} tool contract, contaminating that version
number. Bumping both SDKs to 0.5.1 restores the "same version = same
contract" invariant promised in the CHANGELOG.

Action required for existing npm consumers: `npm upgrade upjack` to
0.5.1. upjack@0.5.0 will be deprecated with a pointer to 0.5.1.

Python consumers are unaffected — PyPI's upjack was still at 0.4.4 and
0.5.1 is the first release carrying the flat-kwarg contract there.
@mgoldsborough mgoldsborough merged commit 0010306 into main Apr 16, 2026
4 checks passed
@mgoldsborough mgoldsborough deleted the bump-0.5.1 branch April 16, 2026 22:24
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