Prepare Python SDK 2.3.4 heartbeat recovery release - #80
Merged
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
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.
Routine patch release for the merged fenced workflow-task heartbeat retry in #79, tracked by durable-workflow/server#137. The new response is expected from Server 2.4.11; older Servers retain their existing behavior. The general Server compatibility floor remains 2.4.8 because this recovery is optional.
This PR advances Python package, registry, and changelog versions to 2.3.4. The matching Server response is in durable-workflow/server#214; PHP's worker fix is merged in durable-workflow/sdk-php#78 with its own release PR. Rust has no workflow-task heartbeat route. Existing consumers pinned to prior SDK versions need an explicit update and qualification.
Local release metadata and storage-admission tests pass (102 tests);
git diff --checkpasses. Require this PR's complete CI and isolated integration before tagging. After merge, create immutable tag2.3.4at the merge commit, verify the exact PyPI wheel and installed source identity, and use exact published packages and Server image for the #137 MySQL interruption retest. The earlier Swoole result remains failed until that retest; the Apache two-hour diagnostic is separate.