From c3416e0e07c35341dfc2cdefd0517b8cbb4518bd Mon Sep 17 00:00:00 2001 From: Richard McDaniel <1130888+rmcdaniel@users.noreply.github.com> Date: Mon, 2 Nov 2026 18:32:50 -0600 Subject: [PATCH] Prepare Python SDK 2.13.0 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 --- CHANGELOG.md | 2 ++ docs/guides/worker-health.md | 3 +-- docs/reference/worker.md | 3 +-- docs/sdk-reference.md | 2 +- pyproject.toml | 6 +++--- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4c3096de..19ecddbd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] +## [2.13.0] - 2026-11-03 + ### Added - `Worker.status()` returns a read-only `WorkerStatus` snapshot for health diff --git a/docs/guides/worker-health.md b/docs/guides/worker-health.md index 9bd1c1a7..6ab17834 100644 --- a/docs/guides/worker-health.md +++ b/docs/guides/worker-health.md @@ -5,8 +5,7 @@ application health endpoint or an orchestrator probe. It reports this worker's own registration and local progress. A healthy Server, or another worker on the same queue, does not make this worker ready. -This API is in unreleased SDK source. Published packages need the release -that includes it. +This API is available in Python SDK 2.13.0 and later. ## Ready versus live diff --git a/docs/reference/worker.md b/docs/reference/worker.md index adf579d0..568a38d9 100644 --- a/docs/reference/worker.md +++ b/docs/reference/worker.md @@ -31,8 +31,7 @@ execution; selecting a default thread does not enable that protocol. ## Bounded failure reports -This behavior is available in unreleased SDK source. Published packages still -need the compatible release before these limits apply. +This behavior is available in Python SDK 2.11.0 and later. Failure reports retain at most 62 KiB of UTF-8 message text, 128 KiB of stack text and 64 KiB of serialized details and diagnostics. These budgets include diff --git a/docs/sdk-reference.md b/docs/sdk-reference.md index 9825973c..7ea6a91e 100644 --- a/docs/sdk-reference.md +++ b/docs/sdk-reference.md @@ -711,7 +711,7 @@ failure; the verifier does not repair or silently coerce those bytes. A bundle exported after retention cleanup pruned the run's details carries `workflow.details_state: "pruned"`, `history_complete: false` and no history -events. Starting with unreleased SDK source, verification fails it with the +events. Starting with Python SDK 2.13.0, verification fails it with the `history.details_pruned` error, matching PHP Core: such a bundle has no history to replay or import, even though its workflow status stays terminal. Bundles marked `retained`, and older exports without the field, are unaffected. Pruned diff --git a/pyproject.toml b/pyproject.toml index b1bc8a38..9015e53e 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "durable-workflow" -version = "2.12.4" +version = "2.13.0" description = "Python client and worker SDK for Durable Workflow Cloud and self-hosted Server" readme = "README.md" requires-python = ">=3.10" @@ -79,8 +79,8 @@ durable-workflow-replay-conformance = "durable_workflow.replay_conformance:main" durable-workflow-workflow-updates-conformance = "durable_workflow.workflow_updates_conformance:main" [tool.durable-workflow] -product-train = "2.12.4" -registry-version = "2.12.4" +product-train = "2.13.0" +registry-version = "2.13.0" supported-server-versions = "2.8.0" supported-server-release-baselines = { "2" = "2.8.0", "3" = "3.0.0" } worker-protocol-version = "1.20"