Repository navigation
feat(release): prepare coherent 0.102 successor with separate journal - #4419
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.
Prepare the coherent0.102 successor on its existing release rail while keeping historical0.101 recovery on journal19. Ordinary0.102 uses a separate journal20 destination; authenticated absence does not grant creation or publication.
The canonical engine tool pin now names the published0.101 release. Current package notes describe0.102 SDK-installed engine identity pairing and preserve the standing advisories and history pointer. Existing archives stay immutable.
Validation: the six affected source suites passed before these two metadata corrections; the unchanged SDK-install four-case harness passed hostedCI on the adapter delivery. The two corrected release gates still require the new exact-head event. Fresh candidate qualification, journal admission, publication and installed original-input recovery remain pending.
Architecture-map impact: none; existing release and adapter boundaries.