chore(release): @uniqent/builder + @uniqent/cli 0.2.0#10
Merged
Conversation
…credentials) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Bumps
@uniqent/builderand@uniqent/clifrom0.1.2→0.2.0for the new CLI auth features (login/logout/publish,publishBundle, stored-tokenpublish-memory).Both bump together because the CLI's new
publishcommand importspublishBundlefrom@uniqent/builder(workspace dep), so the published CLI must resolve to the new builder.To release after merge: ensure the
NPM_TOKENrepo secret is set, then push the tag —git tag v0.2.0 && git push origin v0.2.0— which triggersrelease.ymlto publish both packages to npm.Verified locally:
pnpm build,pnpm typecheck,pnpm testall green;pnpm install --frozen-lockfileclean.🤖 Generated with Claude Code