chore(release): v0.12.6 โ€” TUI keybindings work again

Merged
SA
2mo ago
+40-3

Issue for this PR

Release PR for a hotfix: no issue. 0.12.5 shipped a TUI where, for anyone signed in to Altimate, no keybinding works and Ctrl+C does not quit.

Type of change

  • Bug fix
  • Other: release

What does this PR do?

Two commits on top of main (783920187a, v0.12.5):

  • fix(tui): take the workspace welcome section off the start screen
    • #1381 turned workspaces on by default. Resolving its merge with #1312 registered the boot-box welcome section (workspace-welcome.tsx) for every signed-in user. Before that it ran only for opt-in pilot users.
    • Once that section's binding lookup (resolveBindingOutcome) ran on the home screen, every keybinding stopped working: Ctrl+C, Ctrl+D, Ctrl+P and Esc. Typing still worked. The process stayed idle (about 1% CPU) with the terminal still in raw mode, and never exited.
    • The section is no longer registered. The /workspace menu, the sidebar tile and the rest of workspaces are unchanged. The root cause inside the section is still open.
  • release: v0.12.6: the CHANGELOG entry, with a support note giving ALTIMATE_DISABLE_WORKSPACE=1 as the stopgap on 0.12.5.

Already done: the GitHub "latest" release points back at v0.12.4, so the install script and altimate-code upgrade serve 0.12.4 until this ships. npm latest is still 0.12.5; publishing 0.12.6 moves it.

How did you verify your code works?

How it was found: the post-release E2E against the published @altimateai/altimate-code@0.12.5. It runs the real TUI in a pseudo-terminal, presses keys and measures the redraw.

BuildCtrl+P / Esc / Ctrl+CExits on Ctrl+C
npm 0.12.5no outputno (still running after 70 s)
npm 0.12.5 with ALTIMATE_DISABLE_WORKSPACE=1redraws0.2 s
0.12.5 source without the welcome sectionredrawsyes
0.12.5 source with the section but no binding lookupredraws0.2 s
compiled 0.12.6, home screenredrawsyes
compiled 0.12.6, inside a session (sidebar mounted, after a real prompt)redrawsyes

Release gates run locally on this branch:

  • bun script/release-preflight.ts --version 0.12.6 --stage tag: 9 PASS, 0 WARN, 0 FAIL.
  • bun turbo typecheck: 13/13. Marker guard: clean.
  • Release-critical tests (test/branding/, test/install/) and test/altimate/plugin: 542 pass.
  • OPENCODE_VERSION=0.12.6 bun run pre-release: all checks pass. The compiled binary, run from /tmp with no NODE_PATH, reports 0.12.6. The cold-start config regression passes against it.
  • New test tui-plugin-list.test.ts:
    • With workspaces on, the sidebar is registered and the welcome section is not.
    • With the kill switch set, no workspace plugin is registered.
    • The test fails with the fix reverted.
  • Full suite, dbt-tools checks and the Verdaccio sanity suite: running now; results will be added in a comment.

Screenshots / recordings

N/A: no UI added. The start screen loses the workspace section.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

๐Ÿค– Generated with Claude Code

https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV


Summary by cubic

Release 0.12.6 hotfix that restores TUI keybindings for Altimate users, broken in 0.12.5, and ships the changelog entry.

Bug Fixes

  • Removes the workspace welcome section from the start screen; with it mounted, once its binding lookup ran every keybinding (Ctrl+C, Ctrl+D, Ctrl+P, Esc) stopped working and the TUI could not be quit. Typing still worked.
  • Everything else about workspaces is unchanged: /workspace menu, sidebar tile, and all workspace features remain.
  • Adds a regression test covering which TUI plugins register with and without the ALTIMATE_DISABLE_WORKSPACE kill switch, confirming the welcome section stays out and the /workspace menu stays in.

Summary by CodeRabbit

  • Bug Fixes
    • The workspace welcome section is no longer shown on the start screen. This addresses an issue that could prevent signed-in users on version 0.12.5 from exiting the TUI after workspace lookup.
    • Other workspace features, including workspace navigation and the sidebar, remain available.
    • Upgrade to version 0.12.6 to receive the fix. Setting ALTIMATE_DISABLE_WORKSPACE=1 also disables workspace features.