Repository navigation
chore(release): prepare 0.4.3 - #48
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.
Prepare npm 0.4.3 by updating the root package, published CLI package, and CLI runtime version together. This release includes #43 (clean prompt shutdown, with a maintainer-added Ctrl-D editing regression) and #47 (output-aware loop detection); it does not change dependencies or runtime behavior beyond those merged fixes.
Validation: frozen install, typecheck, build, the complete 1,676-test suite across 97 files with two workers on Apple Silicon macOS, and tool-schema lint. The built CLI reports
0.4.3. The fixes were also checked against their base revisions with real built CLI processes and local HTTP/SSE fixtures; #43 was visually checked in xterm.js 6.0.0 connected to a real macOS PTY.After this PR and its main CI pass, tag
v0.4.3will trigger the existing npm OIDC/provenance publishing and GitHub Release workflow. The registry package will then be installed in an isolated prefix and smoke-tested before the release is announced.