Repository navigation
fix(tui): bump @opentui/core packages to 0.6.4 - #1442
Merged
TheGreatAxios merged 4 commits intoOct 15, 2026
Merged
Conversation
Contributor
|
Superseded by the comment below. |
Contributor
|
Superseded by the comment below. |
Contributor
|
Superseded by the comment below. |
…ump-opentuicore-0512-0517-064 # Conflicts: # bun.lock
Contributor
|
Triage: Pass No changes needed from you. A maintainer will review this pull request. |
SyntaxStyle.destroy frees the native style and nothing finalizes it. Destroying on cache overwrite use-after-frees a style the rows or prompt still paint, so the previous style stays queued until they drop it.
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
@opentui/corepins (core + 8 platformoptionalDependencies) andbun.lockin two stages: commit 1 moves 0.5.12 → 0.5.17 (pin-only, non-breaking: text-buffer leak fix, layout rerender-loop fix, tmux capability-reply fix, OSC-8 hyperlink detection in more terminals). Commit 2 moves 0.5.17 → 0.6.4, the breaking native-scene cutover, and adapts the fallout.SyntaxStyle.fromStyles(); the transcript and prompt syntax styles are now constructed per-renderer (WeakMap keyed on the live renderer, generation-counter theme invalidation preserved), which also removes a cross-renderer style leak the old module-global cache carried.width-contract.tsbuilds its throwaway measure context the way 0.6.4 context-owned buffers demand (1x1OptimizedBuffer+ self-destroyingResourceContext), keeping the never-fatal width-contract contract.url-links.tsguardsonMouseOutagainst the 0.6.x lazy over/out refresh, which synthesizes outs between press and release with an unchanged pointer and could swallow link click-to-open.OutputBusy) by degrading to one more poll round; readiness predicates still decide pass/fail./right after the Ctrl+C arm-flash opening the popup is now pinned by a regression test; the smoke surfaced a pre-existing (pre-bump, reproducibly on the 0.5.17 baseline) Ctrl+C quit wedging with MCP servers — dispositioned and tracked separately as CL-10710, not a 0.6.x regression.Verification
bun run checkpasses (lint, typecheck, dead-exports, build, projects-dir guard, full one-process suite: 8939 pass / 0 fail across 580 files after the smoke-disposition pin); repeated green within and after review.bun run tui:smokegreen on 0.6.4 plus the scripted smoke above; real-terminal follow-ups stay with the operator (iTerm2/Kitty OSC-8 click, capability replies, kitty image placement, drag-select) per docs/TUI.md's real-terminal requirement.@intx/workflow-deployhoist shake from bun's re-dedupe on any pin change is tracked separately (CL-10681).Fixes CL-10647