Skip to content

Prepare Python SDK 2.13.0 - #231

Merged
rmcdaniel merged 1 commit into
mainfrom
release/2.13.0
Nov 3, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
release/2.13.0

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Release metadata for Python SDK 2.13.0. Its content is already on main: #229 (worker readiness and liveness, fixes #168) and #230 (pruned-bundle verification, fixes #228).

  • pyproject.toml: version, product-train and registry-version become 2.13.0. The Server compatibility declaration is unchanged: scalar 2.8.0, map {"2":"2.8.0","3":"3.0.0"}, worker protocol 1.20.
  • CHANGELOG.md: the Unreleased entries move under ## [2.13.0] - 2026-11-03.
  • Docs: the worker-health guide and the SDK reference's pruned-bundle note now say "Python SDK 2.13.0" instead of "unreleased SDK source". The bounded failure-report note in docs/reference/worker.md was also stale. That behavior first shipped in 2.11.0, so it now says that.

tests/test_release_metadata.py passes 42/42 in a python:3.12 container. CI runs the full check_release_metadata.py --source-ref … --dist on the built wheel and sdist.

The sdk-python agent is offline, so General prepared this. After merge, General tags 2.13.0 (the tag push publishes to PyPI) and runs installed verification against native Server.

🤖 Generated with Claude Code

Set the package, product-train and registry versions to 2.13.0 and date
the changelog section for worker readiness and liveness status (#168)
and pruned-bundle verification (#228). Docs that still described these
as unreleased source now name the release that ships them; the bounded
failure-report note names 2.11.0, where that behavior first shipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

sonarqubecloud Bot commented Nov 3, 2026

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel merged commit 1a17df3 into main Nov 3, 2026
21 checks passed
@rmcdaniel
rmcdaniel deleted the release/2.13.0 branch November 3, 2026 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

history_bundle_verify accepts retention-pruned history bundles as ok Expose supported worker readiness and local liveness status

1 participant