Skip to content

v0.8.59: release tracker — TUI mouse-report leak, runtime safety, and current issue/PR queue #3063

@Hmbown

Description

@Hmbown

Goal

Ship v0.8.59 as a stabilization + maintainer-queue release after v0.8.58. The release must include the TUI mouse-report input leak fix observed on macOS, then triage the newly tagged maintainer-request PRs and issue mentions before cutting the release.

v0.8.58 release commit timestamp checked locally: 2026-06-10 23:06:44 -0700.

Release-blocking fix: raw SGR mouse reports leak into composer

Observed failure: the composer fills with raw mouse-coordinate tails such as:

;76;20M35;74;22M35;73;23M...

Likely root cause: the terminal/crossterm parser can consume the ESC[< prefix from SGR mouse reports and deliver only the coordinate tail as ordinary Char key events. The existing composer sanitizer stripped these sequences only when app.use_mouse_capture was true. That is not sufficient because a killed/crashed/orphaned TUI, focus recovery race, or host terminal bug can leave mouse-reporting mode active even when the next App instance did not request mouse capture.

Local patch exists on branch fix/tui-mouse-report-leak:

  • crates/tui/src/tui/app.rs
  • make strip_raw_mouse_reports_from_input() run defensively regardless of use_mouse_capture
  • add regression tests for full SGR reports and tail-only bursts when mouse capture is disabled
  • preserve normal coordinate-like text such as Size 12;34M

Acceptance:

  • Land the fix/tui-mouse-report-leak patch or equivalent.
  • Composer strips full SGR mouse fragments like [<35;44;18M even when use_mouse_capture = false.
  • Composer strips tail-only leaked bursts like ;76;20M35;74;22M35;73;23M... even when use_mouse_capture = false.
  • Composer keeps legitimate text like Size 12;34M.
  • Add/keep tests covering composer_strips_* and composer_keeps_* cases.
  • Verify cargo test -p codewhale-tui composer_strips.
  • Verify cargo test -p codewhale-tui composer_keeps.
  • Verify cargo build -p codewhale-tui and cargo fmt -p codewhale-tui --check.

New open issues since v0.8.58

Maintainer review requests tagged for v0.8.59

Clean / likely mergeable after review:

Blocked / needs owner action before merge:

Dependabot review requests tagged for v0.8.59:

Mentioned issues and unread maintainer-attention threads tagged for v0.8.59

Already captured in the earlier mention sweep:

Added from unread GitHub mention notifications on 2026-06-11:

Left out of the v0.8.59 sweep because they are explicitly future-release or roadmap items already tied to v0.9.0: #471, #472, #473, #474, #475, #476, #477, #478, #479, #481, #534, and #582.

Older open PRs with recent activity to decide before release

Suggested release policy

Notes

During local diagnosis, an orphaned /Users/hunter/.local/bin/codewhale-tui process was found under PID 5157 with revoked stdio and 100% CPU. That supports the defensive sanitizer change: terminal/reporting state can outlive the App state that originally enabled it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentationenhancementNew feature or requestrelease-blockerMust be fixed before the next releasev0.8.59Targeting v0.8.59

    Projects

    Status
    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions