Skip to content

Harbor Desk v0.6.0

Pre-release
Pre-release

Choose a tag to compare

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

Harbor Desk v0.6.0 preview

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

Changes

Changed

  • The desktop now accepts one Gateway or Docker Engine target and detects the
    connection type before creating the renderer. Server Gateways are used
    directly; raw Engine targets start a Local Gateway wrapper on a dynamic
    loopback port, so a Server Gateway and an unnecessary local Gateway are no
    longer started together.
  • Connection settings, diagnostics, CSP, REST, and WebSocket routing now use
    the active Gateway uniformly. Remote raw Engines require HTTPS plus CA,
    client certificate, and private key material held by the Electron main
    process.

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

npm distribution

The npm registry provides v0.6.0 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.6.0 -- --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 detects a configured Harbor Desk Gateway or Docker Engine. It uses a Server Gateway directly, and starts a bundled Local Gateway wrapper on 127.0.0.1 only for a raw Engine target. Docker access remains behind a 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.