fix: mark beta-tools as private to skip npm publish#8240
Merged
Conversation
beta-tools is an internal CLI tool and should not be published to npm. The beta publish workflow was failing with E404 because the @bitgo-beta/beta-tools package does not exist on the registry and trusted publishing cannot create new packages. Ticket: BTC-0
louib
approved these changes
Mar 3, 2026
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
2 participants
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
@bitgo/beta-toolsas"private": trueso lerna skips it during publish@bitgo-beta/beta-toolsdoesn't exist on the npm registry and trusted publishing can't create new packagesTest plan
Ticket: BTC-0