Skip to content

chore: release 0.15.0 - #23

Open
scarmuega wants to merge 1 commit into
mainfrom
release/0.15.0
Open

chore: release 0.15.0#23
scarmuega wants to merge 1 commit into
mainfrom
release/0.15.0

Conversation

@scarmuega

Copy link
Copy Markdown
Contributor

Two changes:

  1. sdk/pyproject.toml → 0.15.0. Coordinated fleet cut: sdk-spec/release-policy.md requires all four SDKs to share one MAJOR.MINOR train, and rust/web carry API changes this cycle (with_tx_params; the breaking Ed25519Signer.fromMnemonic removal). This SDK's own delta since 0.14.0 is just the byte-array encoder fix (fix: accept native byte arrays in the bytes arg encoder #22), so the minor is the lockstep's cost, not a signal of breakage here.

  2. .trix/client-lib/requirements.txt.hbstx3-sdk>=0.15.0,<0.16.0. It pinned git+https://github.com/tx3-lang/python-sdk.git@main#egg=tx3-sdk&subdirectory=sdk, so every generated Python client installed whatever main happened to be — no reproducible build, and no way to express the train the generated code was written against. Now it resolves from PyPI within the train, matching what the rust and web templates already do.

Merge, then push v0.15.0 to trigger the publish workflow (it validates the tag against sdk/pyproject.toml).

🤖 Generated with Claude Code

Coordinated fleet cut per `sdk-spec/release-policy.md` ("All SDKs MUST
share the same MAJOR.MINOR release train"): rust and web carry API changes
this train, so python moves with them. This SDK's own delta since 0.14.0 is
the byte-array encoder fix (#22).

Also pins the codegen template's dependency to the released train instead
of `git+...@main` — generated clients tracked the branch, so they could not
reproduce a build or resolve a version.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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