Repository navigation
chore(release): prepare 0.24.0-beta.1 - #1187
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
benvinegar
marked this pull request as ready for review
October 15, 2026 17:02
Contributor
[Low impact] This release-preparation PR appears safe to merge. SummaryPrepares
Reviews (1) · Last reviewed commit: "chore(release): refresh beta.1 and accep..." · Reviewed by Greptile |
This branch was successfully deployed
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
Prepare
0.24.0-beta.1from current main, including #1186's documentation, CLI help, and bundled-skill corrections. The maintainer explicitly approved shipping the known navigation performance tradeoff after attempts to fix it were unsuccessful.acceptedRegressionsaudit trail.Accepted performance tradeoff
interaction-latency/hunk_nav_press_p95_msregressed against beta.0. The earlier snapshot measured 36.35 → 42.33 ms (+5.98 ms, +16.5%); 16 alternating controlled runs each measured conventional medians of 36.86 ms (beta.0) and 43.20 ms (beta.1). A 16-run recheck immediately before #1085 measured 34.93 ms using the benchmark runner's percentile aggregation, implicating sidebar follow as the likely source.The maintainer approved proceeding with the release, retaining correct sidebar following during held navigation and resize. This is a recorded exception, not a claim that the slowdown disappeared. No unrelated regression is accepted.
Validation
Final release tip
74b1faa8passed all PR CI, including full PTY integration, Linux validation/packaging, Windows compatibility, compiled headless portability on macOS/Windows, Nix packaging, and website validation.Fresh five-sample benchmark comparisons pass against stable 0.23.0 (58 existing gated metrics) and beta.0 (61 passing metrics plus the one explicitly accepted navigation exception). The final snapshot measures navigation p95 at 44.55 ms versus beta.0's 36.35 ms; no other metric is waived.
Fresh local validation passed typecheck, lint, formatting, dependency boundaries, generated docs/changelog checks, default tests, TTY smoke, Node broker and review conformance, prebuilt build/packaging, and global-install smoke. The local PTY suite again passed 263 tests, with one platform skip and the same existing comment-target failure documented on beta.0; the full refreshed PTY suite passed in CI.
All 16 Firecracker installation compatibility scenarios passed from the clean final commit.
validate-release-result.tsverified the complete evidence against source identity3995421b3c52a10a29144dd88881648db8c161399e0b76ce0df6cb7429b3a064.Publication will use npm
betaand GitHub prerelease status, leaving stablelatestunchanged.This PR description was generated by Pi using GPT-6.1 (gpt-6.1-sol)