fix(release): classify beta GitHub releases#8
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.
The publish workflow now keeps prerelease tags from becoming GitHub’s Latest release.
Why
Beta npm releases were correctly tagged
beta, but their GitHub releases were created as ordinary releases and displaced the stable Latest pointer.Fixes
make_latestthrough the Releases API for beta tags.Risks & Testing Needed
Workflow syntax: validated with actionlint.
Live metadata: beta.92 and beta.98 are prereleases; v0.17.0 is currently Latest.
Test Plan
Rollback
Revert the commit. Existing release metadata would remain unchanged until edited explicitly.