Harbor Desk v0.3.2
Pre-releaseHarbor Desk v0.3.2 preview
This preview contains the remote-first desktop client and the server-side Docker gateway installer.
Changes
Fixed
- The desktop shell now remains available after a restart or reload while the
remote gateway is offline. Session bootstrap failures use the existing
gateway-unavailable state instead of replacing the whole interface with a
nearly blank error screen.
Changed
- The Windows NSIS installer now uses Harbor Desk application, header, welcome,
finish, and uninstaller artwork; bilingual English/Korean assisted setup;
explicit shortcut, install-scope, destination, and finish behavior; and
branded Add/Remove Programs metadata. - The Windows application explicitly runs as the invoking user, while the
installer keeps optional elevation limited to a user-selected all-users
install. The NSIS GUID is pinned to the identity already shipped in v0.3.1 so
custom branding does not break upgrades. - Release artifact transfer now uses the current Node 24-based
actions/upload-artifact@v7andactions/download-artifact@v8actions. - Generated release notes now include the matching changelog section and report
whether the tagged package is actually available from npm. An attached GitHub
tarball is no longer described as though it were already npm-published. - The README documents how to compare GitHub and npm versions and how to invoke
a downloaded, checksum-verified release tarball explicitly.
Downloads
- Windows: x64 NSIS installer and blockmap
- Linux: x86_64 AppImage and Debian package
- macOS: x64 and arm64 DMG/ZIP packages and blockmaps
- Server: attached GitHub release tarball
harbor-desk-0.3.2.tgz - Integrity:
SHA256SUMScontains SHA-256 checksums for every distributable asset
npm distribution
At release time, the npm registry's latest version was v0.2.0, so an unpinned npx --yes harbor-desk command will not fetch v0.3.2.
After downloading and verifying the attached tarball, run it explicitly:
npx --yes --package ./harbor-desk-0.3.2.tgz harbor-desk --versionPreview 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 desktop client remains remote-first and does not require a local Docker Engine. The server installer supports controlled Linux, Windows, and macOS Docker hosts, but requires explicit --allow-local-engine-socket acknowledgement before mounting a host's Docker Engine socket.
See SECURITY.md for the current security and dependency-advisory boundary.