Skip to content

release(runtime-python): 0.1.28 — ship the cross-tool bridge - #14

Merged
jascal merged 1 commit into
mainfrom
release/runtime-python-0.1.28
May 30, 2026
Merged

release(runtime-python): 0.1.28 — ship the cross-tool bridge#14
jascal merged 1 commit into
mainfrom
release/runtime-python-0.1.28

Conversation

@jascal

@jascal jascal commented May 30, 2026

Copy link
Copy Markdown
Owner

Why

PyPI orca-runtime-python 0.1.27 was uploaded 2026-04-17, six weeks before the cross-tool bridge merged (#13, 2026-05-29). So the published 0.1.27 does not contain register_foreign_runner or the bridge module — yet main was still labeled 0.1.27. A consumer doing pip install orca-runtime-python gets a runtime with no bridge.

This bumps to 0.1.28 so the bridge is actually released, and re-syncs the lagging __init__.__version__ (it had drifted to 0.1.26).

Changes

  • pyproject.toml: version = 0.1.27 → 0.1.28
  • orca_runtime_python/__init__.py: __version__ = 0.1.26 → 0.1.28

No code changes — version metadata only.

Verification

  • pytest packages/runtime-python/tests/106 passed
  • python -m build → sdist + wheel; twine checkPASSED (both)
  • Clean-installed the 0.1.28 wheel into a fresh Python 3.11 venv: register_foreign_runner = True, BRIDGE_PROTOCOL_VERSION = 1.0, importlib.metadata.version == 0.1.28.

Follow-up after merge: tag runtime-python-v0.1.28 and twine upload the built artifacts.

🤖 Generated with Claude Code

PyPI 0.1.27 was cut 2026-04-17, before the cross-tool bridge merged (#13),
so the published 0.1.27 lacks `register_foreign_runner` / the `bridge` module
even though main was still labeled 0.1.27. Bump to 0.1.28 so the bridge is
actually released, and re-sync the lagging `__init__.__version__` (was 0.1.26).

No code changes — version metadata only. 106 runtime-python tests pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jascal
jascal merged commit 1979798 into main May 30, 2026
3 checks passed
@jascal
jascal deleted the release/runtime-python-0.1.28 branch May 30, 2026 03:50
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