Repository navigation
release: Capy CLI v0.9.13 - #397
Merged
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.
Record CLI 0.9.13 in the repository after it was published from this release branch without the required release PR. The public npm artifact and
v0.9.13tag already exist; this PR does not replace them.The published runtime includes PR #396's conflict-resolution changes across write commands and deploys. This branch records the 0.9.13 version, generated CLI reference, callback-free npm approval helper, and Homebrew runner change. The publishing instructions now require a merged release PR, passing CI for the exact main commit, and an artifact built from that commit before npm publication. It also fixes the CI terminal-cleanup test to use a fresh stream instead of pretending the runner's potentially closed stdin is a terminal; all cleanup assertions remain intact.
Published artifact source:
1a95d3107c419a6b5a92862c24809f3cd53a7bb0. The subsequent test-fixture fix changes no runtime code. The Docker Compose forwarding work merged later in #392 is not part of the published 0.9.13 package.Validation: public npm installation reports 0.9.13; its integrity matches the reviewed tarball; edit, push, and deploy expose the new conflict options. All five standalone binaries and checksums were built and uploaded, including a Linux smoke test without Node. The stdin regression reproduces before the fix and passes afterward on Bun 1.4.3. Full PR CI passed for head
52183a4ee066a60175c3104ef5b57510406c8998: typecheck, build, the full test suite, npm approval tests, and screen checks. Security Scan and CodeQL also passed. PR CI: https://github.com/capysc/capy-cli/actions/runs/39609127381.