Repository navigation
Release Python SDK 2.20.0: signal-with-start and durable signal-external - #349
Merged
Merged
Conversation
Ships signal-with-start (#347, .github#222) and durable signal-external (#346, .github#223). Both need native Server 3.15.0 or later; they are capability-gated, so the supported Server baselines stay unchanged and the requirement is documented in the CHANGELOG and docs. Retargets the installed retry-cap qualification cell to the 2.20.0 candidate on native Server 3.15.0 (index sha256:f7f84884..., source fdb6c4f6, amd64 sha256:0d0db083...). Co-Authored-By: Claude Opus 5.5 <[email protected]>
Records build-only run 44583674899 (attempt 1) at d5e6e63: its dist-handoff.tar artifact and the exact wheel and sdist reviewed against the source and qualified on native Server 3.15.0. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Member
Author
|
Candidate review. Build-only run 44583674899 (attempt 1) built head
Qualified on native Server 3.15.0 (
🤖 Generated with Claude Code |
|
Member
Author
|
Published.
🤖 Generated with Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Prepares the Python SDK 2.20.0 release from current
main(c593df85, which includes #347 and #346). Not tagged or published. Open #348 is not included.What ships (since 2.19.1)
Package changes since 2.19.1 are #347 and #346. Both add public API with no breaking change, so this is a minor release.
Client.signal_with_start()(Add Client.signal_with_start for atomic intake (.github#222) #347, .github#222): start-or-reuse plus one signal in a single Server transaction.ctx.signal_external_workflow()(Let workflow code signal another workflow durably #346, .github#223): workflow code signals another workflow durably, recorded once in history.Server requirement
Both need native Server 3.15.0 or later, the first Server that advertises
capabilities.signal_with_startand thesignal_external_workflowworker command. Each call is capability-gated and refused before anything is sent on an older Server (RuntimeCapabilityUnsupported, or the workflow task fails withsignal_external_workflow_unavailable). Every other feature keeps working on older Servers, and worker protocol (1.20) and control-plane (2) are unchanged in Server 3.15.0, so the SDK-widesupported-server-versions/supported-server-release-baselinesstay as they are. The requirement is documented in the CHANGELOG,docs/sdk-reference.md(new Signal-with-start section and a feature/Server table under Compatibility) anddocs/reference/workflow.md.Release metadata
Version metadata
2.20.0, CHANGELOG section[2.20.0] - 2026-11-19, and the installed retry-cap cell retargeted to the 2.20.0 candidate on native Server 3.15.0 (indexsha256:f7f84884…inghcr.io/durable-workflow/serveranddurableworkflow/server, sourcefdb6c4f6, amd64sha256:0d0db083…).Remaining steps (same as 2.19.x, #342/#345)
.github/release-candidates/2.20.0.json.ci.ymlrun withactivity_retry_cap=true,retry_cap_artifact_source=candidate.--match-head-commit).2.20.0, which triggerspublish.yml. Then verify PyPI and run the registryci.ymlrepeat onmain.🤖 Generated with Claude Code