Repository navigation
docs: repair Server560 publication note boundary - #400
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
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.
The Server560 publisher stopped before image construction because its candidate note lacked the existing
Verified component inputsboundary. Restore that exact boundary and keep the verified coordinates plus behavioral, pending-acceptance and rollback sections inside the renderer output.Validation: the exact failed
PublicationNotes.test_actual_current_release_note_has_the_required_evidence_boundarynow passes. Runtime files, component pins and all other previously passed checks are unchanged; the original failed publisher40989595777 log is retained.