Prepare Server 2.4.11 heartbeat recovery release - #215
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.
Prepares routine Server 2.4.11 and Helm chart 0.1.106 from the merged workflow-task heartbeat backend recovery in #214, tracked by #137. The published 2.4.10 Swoole interruption fixture returned HTTP 500 on this route and the PHP SDK worker exited, leaving 28 acknowledged runs pending at the deadline. The fix returns a typed 503 with the exact task, lease owner and attempt fence. The old result remains a failed experiment until exact published artifacts pass a repeat.
The source-release record advances both versions; its generator synchronized 24 version consumers. The Server image keeps the same locked Workflow package. Server does not embed the PHP or Python SDK packages; their retry changes are merged in durable-workflow/sdk-php#78 and durable-workflow/sdk-python#79 and have separate release PRs. Rust has no workflow-task heartbeat call. Existing pinned consumers need explicit updates and qualification. Cloud deployment decisions remain private and independent of this Server release.
Local checks: source-release sync
--checkandgit diff --checkpass. The #214 feature, contract, public-boundary and source-qualification checks passed before merge. Require this PR's feature, release metadata, chart, public-boundary and performance checks before tagging. After merge, create immutable tag2.4.11at the release merge commit, verify both published image registries and Helm chart, then retest the short MySQL stop/restart against the exact published Server/PHP SDK tuple for Apache, Swoole and OpenSwoole. The Python SDK must be covered by its changed protocol conformance; the independent two-hour Apache diagnostic remains pending.