🔧 Unify CLI beta releases#323
Merged
Merged
Conversation
Publish beta builds through the same workflow npm trusts for stable releases, while keeping the manual trigger focused on explicit release types.
Robdel12
marked this pull request as ready for review
July 22, 2026 16:56
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.
Why
npm allows only one trusted publisher workflow per package, so the separate beta workflow could not authenticate while
release.ymlowns the package's trusted-publisher connection. That workflow also exposed release Git state before proving the package could build and publish.Approach
Keep one manual
Releasetrigger and addbetabeside the existing patch, minor, and major choices. The beta choice creates the nextbetaprerelease, publishes it under the npmbetadist-tag, and marks the GitHub release as a prerelease while preserving the stable release path and its publish-first ordering.The obsolete beta workflow is removed, along with the
currentrecovery mode that existed for the older push-before-publish flow.Evidence
The unified workflow parses successfully and preserves the existing unpublished-version check, build, and npm publish before pushing the version commit or tag. Stable releases remain the default and continue publishing without a prerelease dist-tag.