Skip to content

release: v0.1.1 - #142

Merged
FelineStateMachine merged 2 commits into
mainfrom
release/v0.1.1
Jul 26, 2026
Merged

release: v0.1.1#142
FelineStateMachine merged 2 commits into
mainfrom
release/v0.1.1

Conversation

@FelineStateMachine

Copy link
Copy Markdown
Owner

Ships the two fixes from the end-to-end test on live hardware (#137, #140), both merged via #139.

  • Control v2 disconnected on its first input ack — clicking to control always dropped the session
  • Shadow mode detached viewers it had disabled the remedy for — ended sessions ~25s in, on the configuration the activation guide writes

Both verified against a Bazzite host running the published v0.1.0: the session is now stable, and audio and controller turned out to be game-side rather than goq bugs (#141 closed).

Version pins

website/install-sigil pins one immutable release tag, so it moves to v0.1.1 in the same commit as the three crate versions — otherwise the public install command keeps serving 0.1.0.

package-bazzite-product-contract.sh asserts the tag matches the Sigil version. Its fixture tag and its deliberate mismatch case move with the bump.

Verified

fmt, 473 Rust tests, 30/30 shell tests, sigil_bootstrap_channel=open, website_static_gate=ok.

Ships the two fixes that made a real session usable, both found by running the
published v0.1.0 against live hardware rather than through the proof harness.

Control v2 rejected the host's first input acknowledgement and tore the session
down, so clicking to control always disconnected. Shadow-mode adaptive then
detached the viewer for failing to recover from a reduction it had never been
allowed to apply, which ended sessions ~25 seconds in on the configuration the
activation guide writes.

`website/install-sigil` pins one immutable tag, so the bootstrap moves to
v0.1.1 in the same commit as the crate versions. The Bazzite product contract
test asserts tag and version agree; its fixture and its deliberate mismatch case
move with them.
verify-portal-release.py requires tauri.conf.json's version to equal the release
tag. It carries its own version field rather than inheriting from Cargo.toml, so
the v0.1.1 bump missed it and the Portal release policy job refused the tag.
@FelineStateMachine
FelineStateMachine merged commit 6b547ee into main Jul 26, 2026
26 checks passed
@FelineStateMachine
FelineStateMachine deleted the release/v0.1.1 branch July 26, 2026 02:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant