Repository navigation
Check the actual release note before publication - #357
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.
Server550 completed its build, security, startup/restart, image push and attestations, but its candidate note omitted the renderer's required component-evidence heading. Add that heading and validate the actual current candidate note during the existing pre-build release-note tests, so a fixture-only test cannot miss the same error again.
All four focused renderer tests pass. This is a documentation/validation change; it does not change or rebuild the already published image. The original failed run remains recorded, and its exact signed image and original CI evidence will be retained when completing Release publication.