Repository navigation
feat(release): add releaseType and yes options for non-interactive release - #51
Merged
Merged
Conversation
…lease `vr release --release-type patch --yes` skips the release type prompt and the refs/registry confirmations, so CI and AI agents can release without a TTY. Co-Authored-By: Claude Opus 5.5 <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
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
vr releaseis interactive only, which blocks CI jobs and AI agents that have no TTY. This adds two options torelease:--release-type <type>(releaseTypein the Node API): one ofpatch,minor,major,prepatch,preminor,premajor. Skips the release type prompt and the version confirmation. An invalid value throws and exits with code 1.-y, --yes(yes): skips the git refs and npm registry confirmations. The refs, registry and version change are still printed withlogger.info.They can be used separately:
--release-typealone still asks for the refs/registry confirmations, and--yesalone still asks for the release type.pnpm exec vr release --release-type patch --yesBoth READMEs document the new flags.
Test plan
pnpm build,pnpm type-checkvp test run: 135 passed. New cases cover the flag passthrough, patch/minor/major with no prompts,releaseTypewithoutyes, and an invalid typevr release --release-type minor -y --skip-npm-publishbumped 1.2.3 → 1.3.0, generated the changelog and pushed the commit andv1.3.0tag;--release-type hugeexited with code 1🤖 Generated with Claude Code