Repository navigation
v0.12.0 — qualified stable release
This release supersedes v0.11.0 as GitHub Latest. Its signed candidate qualification is recorded in docs/RELEASE_STATUS.md; planned combinations below are not evidence until that campaign passes. Supported platform families (Linux, macOS, and Windows hosts; Chromium-based browsers, Firefox, and Safari/WebKit) are tested in CI, not qualified; see docs/COMPATIBILITY.md. Neither claims unnamed hosts, browsers, OMP builds, or remote-access paths.
Highlights since v0.11.0
- This release uses stock OMP v18.20.0 as its engineering baseline. The 5 changelog entries below record the changes since v0.11.0. Historical receipts do not qualify these bytes.
- Rewrite the README and documentation for their readers: the usage guide follows the app's current screens, the operations guide puts the one-host path before optional features, and dated records move to labeled tails in each document.
- Advance the independent host engineering baseline to stock OMP 18.20.0 with measured source and native pins; retain the minimum host and published qualification.
- Refresh the embedded client and wire dependency to exact OMP 18.20.0 source: bounded guest resync, HTML-form Ask and named task/step results, with local safety patches and older-host rendering retained; show the host's result text for a form Ask without answers, and open a subagent transcript only by the agent id the host reports; recognize its positive counted rewind status in the canary without accepting failed or zero-turn text.
- Correct documented names and paths: the push state file is
push-state.json, the Windows scheduled task isOMP Session Gateway, a custom OMP discovery directory is~/<PI_CONFIG_DIR>/run/collab-hosts, anddoctorruns up to three conditional checks. - Run the Windows qualification lane's RDP client without a console display and fail immediately on client exit, with bounded controller-local startup probes and typed cleanup-settled failures.
Qualified combinations
| role | combination |
|---|---|
| Linux host | Run 43539190729 succeeded (https://github.com/carrythroughsystems/omp-session-gateway/actions/runs/43539190729); OS/kernel versions and migration counts are not exported. |
| macOS host | VirtualMac2,1, macOS 27.0 arm64; doctor 18/18, rollback 23/23; native addon 50c4795066df814cea3a0849109dd86c11089f8bccef0736681b29801cdaaa5c. |
| Windows host | Windows x86-64 build 26100; 4 CPUs, 8186 MiB; Administrator upgrade/rollback from v0.11.0 and fresh standard-account lifecycle; interactive logon, not unattended boot. |
| Chrome and Chromium | Pixel 8 Pro, Android 17, Chrome 157.0.8103.46; TestingBot, tunnel 4.9: Galaxy S24 (14.0.0, chrome 154.0.8037.126) |
| Safari and WebKit | TestingBot, tunnel 4.9: iPhone 17 Pro Max (26.6, safari 26.6.1); BrowserStack, tunnel 8.9: iPad (10th generation) (27.0, safari 27.0) |
| Android | Pixel 8 Pro, Android 17, Chrome 157.0.8103.46; TestingBot, tunnel 4.9: Galaxy S24 (14.0.0, chrome 154.0.8037.126) |
| iPhone and iPad | TestingBot, tunnel 4.9: iPhone 17 Pro Max (26.6, safari 26.6.1); BrowserStack, tunnel 8.9: iPad (10th generation) (27.0, safari 27.0) |
Exact qualified OS, browser, and kernel builds, per-lane evidence, and the qualifying candidate are recorded in docs/RELEASE_STATUS.md and docs/COMPATIBILITY.md at this source commit.
Required deployment preconditions
- Install mainline OMP >=18.1.20 (source reference: v18.20.0 at c308970263ae13744ea15ab67302e3dac840e266), set collab.autoStart to control or view, and start sessions with plain omp. No gateway integration patch is required.
- Run Tailscale's TUN-mode client and Tailscale Serve over tailnet HTTPS. Userspace networking, Funnel, Portal Tunnel, and self-hosted or proxied relays are not supported.
Known environment limitation
Android Chrome can wedge its process-wide network state outside the qualified lock/Airplane/Doze transitions. Native EventSource reconnection and the bounded snapshot fallback recover the qualified cases; after an uninterrupted prolonged visible outage the loaded shell exposes force-stop/reopen help. The release does not claim page JavaScript can restart a failed browser process.
The Windows claim is start at interactive logon, not at boot. Background Web Push records force-stop and Doze outcomes as observed variants, never as guaranteed delivery.
Cloud-device clients are qualified in the browser: Tailscale Serve saw the qualification workstation's login, not the phone's own, and iPhone alerts were proven with the device unlocked, not on the lock screen.
Install or upgrade
For the first upgrade from the fork-era gateway, retain its signed archive and matching private configuration, then use that archive's uninstall command to stop and unregister its service. This leaves config and installed runtimes in place; an active fork-era service cannot authenticate with the new readiness token.
Extract omp-session-gateway-0.12.0-bun.tar, then run bun apps/gateway/src/cli.js install --origin https://host.tailnet.ts.net --allow user@example.com with the deployment's real values. Repeat --allow for additional identities. Subsequent mainline reinstalls preserve configuration and the readiness token.
Rollback
The selected predecessor is v0.11.0. Gateway rollback does not switch or restart the separately running OMP process. This release uses stock OMP v18.20.0. rollback --to selects only retained runtimes. Preserve configuration and readiness-token state; see docs/UPGRADE_ROLLBACK.md for predecessor compatibility and stopped-service recovery.
- Source commit: 3d317d7
- OMP source reference: c308970263ae13744ea15ab67302e3dac840e266 (tag v18.20.0); mainline >=18.1.20 is required
- Runtime: Bun 1.4.4; registry protocol 1; Push API 2
- Verification: https://github.com/carrythroughsystems/omp-session-gateway/blob/3d317d7fa5f30f9de206618600994a0417c13a98/docs/RELEASE.md