Skip to content
TeamHUD Docs

Updates and minimum version

  • 0 client builds you publish
  • ~4 h between update checks (macOS, Windows)
  • Soft MIN_CLIENT_VERSION nudges, never refuses

Your server does not serve the client update feed

Section titled “Your server does not serve the client update feed”

Desktop apps fetch updates from TeamHUD’s release host (https://prod.teamhud.app unless the install was pinned to another environment), not from your server. The updater deliberately does not follow the server a user signs in to. The release host is pinned per install, and any self-hosted address maps to TeamHUD’s. Your users update on the same track as everyone else, and you do not publish client builds.

This also means:

  • SELF_HOST_BUNDLE_PATH is not an update feed. It is the storage path of the server bundle that GET /downloads/server hands out (login required), and 404s if unset.
  • The rollout and auto-pin settings do not govern your users’ updates. The server code has a feed route (/updates/...), staged rollout and UPDATE_AUTOPIN_*, but the desktop app does not query your server for them. Leave UPDATE_AUTOPIN_ENABLED at its default (false) on a self-hosted box.

How the app updates

Section titled “How the app updates”
OS Behavior
macOS, Windows Packaged, signed builds download and install updates. First check about a minute after launch, then roughly every 4 hours. Preferences, Updates, Check now checks on demand and shows the install-and-relaunch button once downloaded.
Linux The feed only notifies. Upgrade with apt upgrade, dnf upgrade, or a new AppImage.

Preferences, Updates also has a Release channel selector (experimental, alpha, beta, rc, stable; the server decides which it offers).

MIN_CLIENT_VERSION

Section titled “MIN_CLIENT_VERSION”

Set MIN_CLIENT_VERSION in .env (for example 1.0.0-alpha) to the oldest desktop version you accept without a nudge. Unset means no floor. Versions compare as semver, so a pre-release such as 1.0.0-alpha sorts below 1.0.0.

It is a soft floor. A client below it is not refused or signed out. At password sign-in the server replies updateRequired: true with minVersion, and the realtime connection carries the same flag. The app then shows a persistent warning in the System Issues icon titled Update TeamHUD (“A newer version of TeamHUD is available…”) with an Update button. The warning cannot be dismissed and clears once the client is at or above the floor. Everything else keeps working.