Support beta tags for prebuilt releases#15
Merged
benvinegar merged 1 commit intomasterfrom Mar 21, 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.
Summary
--tag <dist-tag>support to the prebuilt npm publish scriptnpm_taginput through the prebuilt release workflowlatestWhy
PR #14 landed the actual prebuilt npm release workflow, but after merge we still needed a safe beta path so we can publish something like
0.3.0-beta.1under npm'sbetadist-tag before moving stable users offlatest.What changed
scripts/publish-prebuilt-npm.ts--tag <name>npm publish --tag <name>.github/workflows/release-prebuilt-npm.ymlworkflow_dispatch.inputs.npm_taglatestValidation
bun run typecheckbun run build:prebuilt:artifactbun run stage:prebuilt:releasebun run publish:prebuilt:npm -- --dry-run --tag beta