Skip to content

chore(release): bump tx3-sdk to 0.12.0#14

Merged
scarmuega merged 1 commit into
mainfrom
release/v0.12.0
May 24, 2026
Merged

chore(release): bump tx3-sdk to 0.12.0#14
scarmuega merged 1 commit into
mainfrom
release/v0.12.0

Conversation

@scarmuega

Copy link
Copy Markdown
Contributor

Summary

Bumps tx3-sdk to 0.12.0 to align with the fleet's 0.12 release train. The unified-builder port that merged in #13 is a breaking change and per release-policy.md any MINOR/MAJOR change MUST be coordinated across all SDKs (rust-sdk's workspace already declares 0.12.0).

Bumps both pyproject.toml and the runtime __version__ constant in tx3_sdk/__init__.py.

After this lands, a v0.12.0 tag will be pushed to trigger the release workflow → publish to PyPI.

Test plan

  • Two-line version bump, no code change. CI covers everything else.

🤖 Generated with Claude Code

Aligns the python-sdk package version with the fleet's 0.12 release train
(rust-sdk workspace is already at 0.12.0). The unified Tx3ClientBuilder
landed in #13 and is a breaking change — per
sdks/sdk-spec/release-policy.md any change to MAJOR or MINOR must be
coordinated across all SDKs.

Bumps both pyproject.toml `version` and the runtime `__version__` constant
in tx3_sdk/__init__.py.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@scarmuega scarmuega merged commit 282c741 into main May 24, 2026
2 of 3 checks passed
scarmuega added a commit that referenced this pull request Jun 12, 2026
…er invoke path

Behavior-preserving readability pass over the complex param-type interpreter,
mirroring the rust-sdk (#41) and go-sdk (#14) changes.

- Split param_type_from_schema into a thin dispatcher plus _ref_type /
  _array_type / _object_type helpers (joining the existing _variant_case /
  _core_kind_from_ref). Same fallbacks, recursion, and kind map.
- Remove InvalidParamTypeError: the interpreter no longer raises it once it
  became never-failing, leaving it dead. InvalidParamsSchemaError stays
  (protocol.py still raises it).
- Add test_invoke_interprets_complex_params + the shared complex.tii fixture
  to cover the Protocol.invoke path the unit tests can't reach: components
  threading, party->Address, environment params, and a resolved component-$ref
  Record and Variant.

Co-Authored-By: Claude Opus 4.8 (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