Repository navigation
docs: retain the complete published artifact identity - #308
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.
Restore the exact, already-published Server v1.6.535 OCI artifact reference in COMPATIBILITY and its release note. The split manifest/config digests were present, but the existing install-publication contract requires the canonical tag+digest identity in evidence. README and Docker/Compose examples remain numeric tags without digest pinning. No gate, runtime, source producer, image, or security-policy change. Preserve the original failed v1.6.536 source-gate run 38680955022; only after this documentation correction and normal required checks may a new main producer run publish the still-unpublished v1.6.536.