Harbor Desk v0.3.1
Pre-releaseHarbor Desk v0.3.1 preview
v0.3.1 supersedes v0.3.0 for desktop installs.
Fixed in v0.3.1
- Fixed the packaged desktop client opening as an empty dark window. Vite had emitted root-relative
/assets/...URLs, which Electron could not load from the packagedfile://page. - Renderer JavaScript and CSS references are now package-relative (
./assets/...). - Added a regression test that inspects the built renderer HTML and verifies that every local asset reference is relative and resolves to a packaged file.
The Windows x64 installer was also installed over v0.3.0 and smoke-tested locally; the full remote-first Containers UI rendered successfully.
Downloads
- Windows: x64 NSIS installer and blockmap
- Linux: x86_64 AppImage and Debian package
- macOS: x64 and arm64 DMG/ZIP packages and blockmaps
- Server:
harbor-desk-0.3.1.tgz - Integrity:
SHA256SUMScontains SHA-256 checksums for all 14 assets
The attached server tarball is v0.3.1. The public npm registry currently remains at v0.2.0, so npx --yes harbor-desk install-server will not fetch this release until the registry is synchronized.
Verification
- Tag commit:
a59cf3576f1bd4e1ca208e416c244a56a2ffaf81 - Release workflow: all verification and Windows/Linux/macOS packaging jobs passed
- Downloaded Windows installer SHA-256:
773a972d5a3b823393d25a956ea1b1275c6b8cb1e2a0ccbc0e7c6dcabc8ec539 - The downloaded installer hash matches both
SHA256SUMSand GitHub's asset digest
Preview and security boundaries
This remains a prerelease. Desktop binaries are currently unsigned; verify SHA256SUMS before installation and use a source build where signed artifacts are required.
The server installer supports Linux, Windows, and macOS hosts running Docker or Docker Desktop. Harbor Desk remains remote-first and requires explicit --allow-local-engine-socket acknowledgement before mounting a host's local Docker Engine socket.
A known high-severity transitive extract-zip advisory currently affects Electron's install-time build tooling, and no patched npm release is available as of this release. It is not included in the runtime server tarball; see SECURITY.md for the documented boundary.