app/version.txt 6.3.3 -> 6.3.4, plus notes. The tag must equal v<version.txt> or the release build fails on purpose, so the bump comes first. Ships two merged commits: 00e256a (seats are found by probing the seat port block instead of asking the MultiSeat service at 127.0.0.1, which could only ever work with Moonlight running on the host) and 1c5f539 (the PR build pipeline trimmed to the jobs that pass). ⛔ The notes lead with the fact that the discovery change has NEVER BEEN RUN. It compiles under Qt 5.14.1 and Qt 6, and the host side is confirmed -- a seat answers /serverinfo with the name discovery looks for -- but no client has executed this code. The machine it was written on has no Qt toolchain. The plausible failure is client-side: discovery reads the host list every 15s while other paths write to it under a write lock on a thread pool. A pull model was chosen specifically to avoid deadlocking against that, but designed-around is not tested. The notes say so, name the symptom to watch for, and point at 6.3.3 as the way back. Understating that would be the wrong trade for a client binary people install. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SQvL62WkT8xDWXqyjFCGDw

Commits

Commits on Sep 10, 2026

release: 6.3.4