Upgrade OpenTUI to 0.5.1 - #40
Merged
Merged
Conversation
austin-smith
marked this pull request as ready for review
August 4, 2026 08:50
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
1 participant
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/coreand@opentui/reactfrom 0.4.5 to 0.5.1bun-ffi-structs0.3.1Why
OpenTUI 0.5.1 includes renderer lifecycle and frame scheduling fixes, improved error reporting, Windows console output improvements, and new native image support. Reviewing the shipped API declarations found no incompatible changes in the OpenTUI interfaces Spotuify uses.
Impact
No application code migration is required. Core and React remain pinned to the same exact version, and the existing React 19.2 and Bun 1.3.14 setup remains compatible.
Validation
bun test— 1,041 passedbun run typecheckbun install --frozen-lockfilebun run licenses:checkgit diff --check