Repository navigation
Prepare Native 2.4.1 session history patch - #613
Merged
Merged
Conversation
9 tasks done
Member
Author
|
Workflow 2.4.1 is published at The exact source passed full main CI, including quality, coverage and all supported database feature shards. Packagist source and dist resolve that same commit. The published package contract and all 16 supported Laravel/PHP upgrade combinations pass in release verification. Server #303 consumes the published patch through its exact Composer lock. Fixed image publication and installed SDK session qualification remain next under shared #124. |
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.
Release
Prepare the exact Native 2.4.1 package identity for the activity session-history fix in #612.
The fix preserves the original worker-session contract in durable activity history so SDKs can validate cold replay. Existing histories without session metadata stay unchanged.
Normal PR checks and the full main-branch quality cycle are required before tagging. Then verify the immutable tag, Packagist identity, published conformance contract and supported Laravel upgrade journeys. Server must consume this exact published patch before the Rust session increment is advertised.