Skip to content

Prepare Python SDK 2.13.0 #231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rmcdaniel merged 1 commit into from
Nov 3, 2026
Merged

Prepare Python SDK 2.13.0 #231

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
3 changes: 1 addition & 2 deletions docs/guides/worker-health.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
3 changes: 1 addition & 2 deletions docs/reference/worker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/sdk-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
6 changes: 3 additions & 3 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down Expand Up @@ -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"
Expand Down
Loading