[0.4.2] - 2026-05-05
Patch release. Two small fixes on top of 0.4.1.
Fixed
wait-ready --logsrewrites dockur's container-internal VNC URL to the host's mapped port. dockur printsvisit http://127.0.0.1:8006/ to view the screenfrom inside its container, where8006IS the listening port. The host maps that tocfg.pod.vnc_port(default8007, seecore/pod/compose.py's127.0.0.1:{vnc_port}:8006spec), so the URL streamed to the user's terminal pointed at a port only reachable inside the container._drainin_wait_readynow substitutes127.0.0.1:8006→127.0.0.1:{cfg.pod.vnc_port}per streamed line, using the user's actual configured port (so a customvnc_portinwinpodx.tomlis honored). Reported by @xiyeming. Closes #118.- Packaging workflows tolerate the create-release race.
debs-publishandrhel-publishboth ran anEnsure release existsstep that didview || create. Onv0.4.1tag push both jobs hit the view-failed branch in parallel and both successfully calledgh release create; GitHub's release-create POST isn't atomic on tag uniqueness, so two GitHub Releases appeared at the same tag andrelease.yml's subsequentsoftprops/action-gh-releasefailed withtag_name: already_exists, leaving the release page without sdist/wheel attached. The create call is now idempotent: try create, swallow anyalready_existserror, then verify the release is reachable viaview. Whichever workflow wins the race creates the release; the loser's create call no-ops; both proceed to upload assets.