Nightly tests failed

[worktrunk-bot]

Nightly tests failed on 2026-07-22

[worktrunk-bot]

Triaged. The failure is on full-tests (windows-2022, windows) only — 42 tests in integration_tests::switch_picker, all failing with the same error at picker startup:

✗ interactive picker failed: Keyboard progressive enhancement not implemented for the legacy Windows API.

Root cause: the skim 5.1.0 → 5.3.1 bump in #3526 (merged just before this run). skim 5.3.1 tries to enable keyboard progressive enhancement, which crossterm rejects on the legacy Windows console the test PTY presents, so the picker never reaches ready state and every switch_picker test times out.

This is already being fixed — no new PR from me:

• build(deps): hold skim at 5.1.0 — 5.3.1 breaks the picker on legacy Windows #3538 (pin-skim-5-1-0) holds skim at 5.1.0. Its full-tests (windows-2022, windows) job passed, confirming the pin resolves it.
• fix(deps): pin skim to 5.1.0 to unblock Windows picker #3537 (fix/ci-29884002914) is an earlier bot ci-fix PR with the same pin.

Both are open and duplicate each other; landing either unblocks nightly. The 5.3.1-vs-legacy-Windows-console interaction is worth investigating upstream before re-attempting the bump.

Evidence

• Failing run: 29896809898 (schedule, sha 89b58e252). Same sha also failed Windows on the 01:46 push run 29884002914 — two consecutive failures on the merged bump.
• 89b58e252 (chore: bump taiki-e/install-action from 2.83.3 to 2.84.0 #3529, a CI-action bump) is code-identical to 87715c305 (the skim 5.3.1 bump) for the Rust build; the skim bump is the only relevant change vs the last green Windows run at 0958a365b (chore: bump the patch group with 6 updates #3524).
• build(deps): hold skim at 5.1.0 — 5.3.1 breaks the picker on legacy Windows #3538's head e3b558a9e = main + the skim pin; its Windows full-tests passed, isolating skim as the cause.

[max-sixty]

Resolved on main by #3538 (merged 2026-07-22), which pins skim back to =5.1.0.

The failing nightly ran on 89b58e252 about two hours before the pin landed, with skim 5.3.1 in the lockfile. skim 5.3.1 enables crossterm keyboard progressive enhancement, which the legacy Windows console the test PTY presents rejects, so the picker never reaches ready state and all 42 integration_tests::switch_picker tests fail. Post-pin, both full-tests (windows-2022, windows) and test (windows) are green on main, so the next nightly will run on the pinned tree.

Closing as resolved.

This was written by Claude Code on behalf of Maximilian