omnideck v0.1.0-beta.3
Pre-releaseomnideck application v0.1.0-beta.3
This beta repairs two setup conflicts reported against v0.1.0-beta.2 and
bundles OmniDeck CLI v0.11.0-beta.2 from commit a32d3ad95f44.
macOS Podman machine recovery
Podman's macOS libkrun provider can run only one Podman machine at a time.
When another machine such as podman-machine-default is active, setup now
explains the switch, stops that machine without deleting it, and starts the
dedicated omnideck-runtime machine. Stopping the other machine also stops its
running containers; its machine files, images, and containers are preserved.
The visible wording is locked as:
Switching Podman machinesmacOS can run only one Podman machine at a time. Stopping "podman-machine-default" keeps its files but also stops its running containers.
This automatic machine switch is macOS-only. Windows and Linux do not stop an
unrelated Podman machine.
Occupied-port recovery
The CLI now classifies the existing saved-installation message as
PORT_IN_USE. Desktop automatically selects and persists another free local
port, leaves the other installation untouched, and continues without a button
or error screen. The existing progress card briefly shows:
Choosing another private address…Port <number> is already in use
The cross-platform behavior and wording are covered by Desktop unit tests and
real packaged Linux and Windows VM-lab journeys. The disposable tests create a
second saved instance on the active port, prove the user is not asked to act,
and verify successful launch on the replacement port.
Qualification
CLI source, race, vulnerability, six-target build, SBOM, provenance, packaged
binary, and public-release contracts gate v0.11.0-beta.2. Desktop source
policy, frozen UX parity, Rust tests, formatting, Clippy, six pinned sidecars,
native package builds, ten installer contracts, checksums, attestations, and
the independent public release contract remain gates for this release.
Known limitations
Preview packages do not yet carry paid publisher identities. Windows may show
a Microsoft Defender SmartScreen warning, and macOS may require explicit
approval in Privacy & Security. Those trust warnings are distinct from package
corruption, invalid signatures, or application launch failures.