Repository navigation
Prepare stable Python 2.5.7 protocol default - #125
Merged
rmcdaniel merged 3 commits intoOct 12, 2026
Merged
Conversation
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
2 participants
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.
Summary
Part of durable-workflow/.github#180. Backport the reviewed default protocol change from main PR #124 onto published Python SDK 2.5.6 and prepare 2.5.7.
The worker protocol defaults to 1.20, with explicit 1.19 compatibility and unchanged capability opt-ins. This stable package contains no producer APIs from the separate 2.6.0 release candidate. Published tags and frozen tuples remain immutable.
Validation
The equivalent main change passes Python 3.10–3.12 unit, lint, packaging, regression corpus and documentation gates. Its connected integration check is still running. This stable branch receives its own full source qualification before merge/publication, followed by installed PyPI and exact published Server consumer checks.