Repository navigation
release: require reviewed public notes before experimental publication - #57
Merged
sanskarIN merged 6 commits intoNov 7, 2026
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.
Why
Workflow #9 successfully qualified the v0.1.5 VSIX, but the existing
docs/releases/v0.1.5.mdis explicitly a development draft saying Not published. Previously, manual publication would have copied that development draft verbatim into the public GitHub Release.Fix
docs/releases/vVERSION-public.mdin the explicit manual GitHub publishing path; fail closed before creating a release when absent.docs/RELEASING.md.Release safety
No tag, GitHub Release, Marketplace or Open VSX publication is performed. Qualification-only remains the default and continues to upload a temporary VSIX artifact. Stable publication is still blocked.
After merge: Re-run the qualification-only workflow against the new
mainSHA, because the earlier successful run #9 qualified the pre-fix commit.