release: 0.6.5 - #53
Merged
Merged
Conversation
version.txt 0.6.4 -> 0.6.5, plus the notes the release workflow reads. No code changes -- four merged commits ship: #49 (a streaming seat reported Ready), #50 (a streaming standalone Apollo reported idle), #51 (that warning overstated the stall), #52 (the audit gate failed on a registry outage). ⭐ Three of the four are runtime-verified on the reference host rather than only CI-green: #49 Ready -> Streaming in 6s on connect, back in 3s on disconnect #50 streaming signal correct in BOTH directions, including a live stream the old serverinfo check reported as idle #51 266 ms measured, and the person streaming did not notice it⚠️ And master CI was RED before this. 45f46b0 failed on a 400 from registry.npmjs.org, not on our code -- the same commit had passed its own PR 45 minutes earlier and passed locally afterwards. #52 fixed the gate; the master push on b5feaac is green across all three jobs, checked before cutting rather than assumed. That is worth recording: "the tests pass" is not "master is green", and I reported the first while implying the second. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SQvL62WkT8xDWXqyjFCGDw
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.
Cuts 0.6.5.
version.txt0.6.4 → 0.6.5 plus the notes the release workflow reads.No code changes — four merged commits ship:
ReadyThree of four are runtime-verified, not just CI-green
Both user-visible bugs were wrong in the same direction — reporting that nothing was happening while something was. The dashboard showed an active seat as idle and a streaming host as free.
45f46b05failed on a 400 from registry.npmjs.org, not on our code — the same commit had passed its own PR 45 minutes earlier, andnpm ci && npm audit --audit-level=highpasses locally on that exact lockfile.#52 fixed the gate so a transport error is retried and then warned about rather than failing the build, while a genuine finding still fails immediately.
The master push on
b5feaac3is green across all three jobs — checked on the master branch before cutting, rather than assumed from PR runs.That distinction is worth stating: "the tests pass" is not "master is green", and I was reporting the first while implying the second.
Known limitations, carried forward
The notes restate the three that remain: seats capture the RDP surface rather than a dedicated virtual display; tearing a seat down still briefly disturbs a standalone Apollo, now announced rather than silent; and MoonlightVibe seat discovery is fixed in 6.3.4 but has not been run by anyone yet, with the manual fallback documented.
Once merged, pushing
v0.6.5publishes. The workflow refuses a tag that disagrees withversion.txt.🤖 Generated with Claude Code
https://claude.ai/code/session_01SQvL62WkT8xDWXqyjFCGDw