Prepare PHP SDK 2.1.2 heartbeat recovery release - #79
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
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.
Routine patch release for the merged fenced workflow-task heartbeat retry in #78, tracked by durable-workflow/server#137. The new response is expected from Server 2.4.11; older Servers retain their existing behavior. The SDK's general Server compatibility floor remains 2.4.0 because this recovery is optional.
This PR advances the PHP package identity, quickstart version, and changelog to 2.1.2. No Workflow package or other SDK change is bundled. Server's matching protocol response is in durable-workflow/server#214; Python's independent worker change is in durable-workflow/sdk-python#79. Rust has no workflow-task heartbeat route to update. A pinned downstream application needs its own dependency update and qualification; a new SDK tag does not alter an existing image or deployment.
Local checks: release metadata and lease retry tests pass (12 tests, 103 assertions); Composer manifest validation and
git diff --checkpass. Require this PR's complete CI before tagging. After merge, create immutable tag2.1.2at the merge commit, verify Packagist resolves that exact source, and retest MySQL interruption with the exact published PHP SDK and Server artifacts across Apache, Swoole, and OpenSwoole before claiming #137's recovery gate. The separate two-hour Apache diagnostic remains independent.