Publish successful GitHub releases - #6
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.
Summary
Root cause
The release workflow passed
--drafttogh release create, sov1.1.0andv1.2.0remained hidden drafts even though their Docker images and release assets were produced successfully. This leftv1.0.4displayed as Latest.Impact
Future successful release workflows will expose their generated notes, SBOM, license bundle, and corresponding-source assets immediately and update the repository's Latest release marker.
Verification
v1.2.0draft and confirmed it is nowisLatest: truev1.2.0release assets remain attachedgit diff --checkgh release createsupports--latest