Repository navigation
Prepare C3 receiver-first coherent 0.103 successor with frozen original recovery - #4448
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
1 participant
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.
C3 continuation source is delivered, while the release rail still selects the published 0.102.0 cut. Select coherent 0.103.0 with predecessor 0.102.0 and a fresh utel-rel-21 journal using the existing candidate and publisher route. Keep explicit original 0.102.0 recovery bound to its retained candidate and consumed utel-rel-20; the CLI profile remains mutually exclusive with all earlier recovery routes.
Validation: six maintained offline release suites passed 165 cases with clean owned-process retirement and complete post-run input checks. After restoring an unrelated historical collision fixture unchanged, the affected candidate suite passed all 13 cases again. The first hosted notes gate found a duplicate prior-version heading; after replacing that entry and preserving all standing advisories, the real MSBuild release-notes fixture passed all 31 cases under maintained owned-process custody. The original failure remains retained. Five sealed historical workflows, the original 0.102 manifest and the four publication policy modules remain byte-identical.
Publication, installed receiver acceptance and the real more-than-40-request provider journey remain pending. This source PR creates no release effect or installation. Fresh collision, exact candidate and operation-specific admission remain required. The registry published-pin discrepancy is retained for its owning durable update.
architecture-map: unaffected