Skip to content

fix(tui): bump @opentui/core packages to 0.6.4 - #1442

Merged
TheGreatAxios merged 4 commits into
mainfrom
cl-10647-tui-staged-bump-opentuicore-0512-0517-064
Oct 15, 2026
Merged

TheGreatAxios merged 4 commits into
mainfrom
cl-10647-tui-staged-bump-opentuicore-0512-0517-064

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Collaborator

Summary

  • Bumps all nine @opentui/core pins (core + 8 platform optionalDependencies) and bun.lock in 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.
  • The 0.6.4 native-scene rewrite requires an explicit resource owner for 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.ts builds its throwaway measure context the way 0.6.4 context-owned buffers demand (1x1 OptimizedBuffer + self-destroying ResourceContext), keeping the never-fatal width-contract contract.
  • url-links.ts guards onMouseOut against 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.
  • Two capture-poll test helpers tolerate the new session-buffer lease window (OutputBusy) by degrading to one more poll round; readiness predicates still decide pass/fail.
  • Scripted tmux smoke at 80x24 against the bumped build: launch/landing geometry, slash + model + mcp palettes, wrapped caret row, transcript sticky scroll + wheel, URL hover-arm + click-open all PASS with capture-pane evidence; a / 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 check passes (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.
  • Commit 1: no src changes, known-frame capture suites (landing, transcript-anchor, overlay-paint) and mouse suites (url-click, mouse-reporting-disabled) green on 0.5.17.
  • Commit 2: full suite + bun run tui:smoke green 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.
  • The bun.lock diff is @opentui-only; a deterministic unrelated @intx/workflow-deploy hoist shake from bun's re-dedupe on any pin change is tracked separately (CL-10681).

Fixes CL-10647

@linear-code

linear-code Bot commented Oct 15, 2026

Copy link
Copy Markdown

CL-10647

@corbits-triage

corbits-triage Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Superseded by the comment below.

@corbits-triage

corbits-triage Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Superseded by the comment below.

@corbits-triage

corbits-triage Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Superseded by the comment below.

…ump-opentuicore-0512-0517-064

# Conflicts:
#	bun.lock
@corbits-triage

corbits-triage Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
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.
@TheGreatAxios
TheGreatAxios merged commit ad86ed7 into main Oct 15, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant