Repository navigation
Release Rust SDK 3.0.0 with cooperative cancellation - #61
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.
Purpose
Publish Rust SDK 3.0.0 for shared cancellation #136. The major release decision is approved.
This changes package/product train and exact qualified Server version to stable 3.0.0 / Server 2.5.0, and gives the unchanged release notes the matching stable heading. Runtime code matches published 3.0.0-rc.1. Existing protocol compatibility remains the authority.
Registry-only mixed cancellation passed 236 assertions. The PHP parent and Python child finished Cancelled with completed cleanup 19.185557 seconds after the original request, before its original 30-second deadline. Actual activity stop without application heartbeats, cleanup-worker SIGKILL/replay, stale result fencing, duplicate identity/deadline and API/CLI inspection passed.
Keep draft until normal checks pass and stable Server 2.5.0 is published. Then merge, publish the exact stable crate and verify registry/MSRV consumers and the stable tuple. Shared #136 remains open through published stable conformance.