Skip to content

Harbor Desk v0.5.3

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 29 Aug 01:43
· 65 commits to main since this release

Harbor Desk v0.5.3 preview

This preview contains the client-first desktop app with its automatic loopback policy gateway, plus the optional server-side Docker gateway installer.

Changes

Added

  • The default server-side npm exec --yes harbor-desk command now opens a
    keyboard-driven TUI when run from an interactive SSH session.
  • The TUI supplies safe defaults, detects the server Docker socket as the
    common connection, keeps remote Engine mTLS as an advanced choice, validates
    the configuration, and prints SSH tunnel plus Gateway/WebSocket connection
    information after installation.
  • install is now an alias for install-server; non-interactive sessions fail
    with explicit SSH guidance instead of waiting for input.

Changed

  • Server setup no longer opens a browser or requires users to assemble long
    installation arguments for the normal interactive path. Explicit options
    remain available for automation.

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.5.3.tgz
  • Integrity: SHA256SUMS contains SHA-256 checksums for every distributable asset

npm distribution

The npm registry provides v0.5.3 under the preview dist-tag (the default latest dist-tag is unchanged). To run that exact version instead of following the latest dist-tag:

npm exec --yes harbor-desk@0.5.3 -- --version

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 desktop starts its bundled gateway automatically on 127.0.0.1 and does not require a local Docker Engine. Docker access remains behind the gateway; the renderer never receives a Docker socket or direct Engine connection. The optional 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.