Release Channel

Last updated

server_settings.release_channel. Server-wide singleton, admin-only. Read by the panel and the agent when they check for updates.

Values

ValueBehavior
stable (default)Tracks the git tag stable — only promoted, reviewed builds. If no stable tag exists yet, the update check reports “up to date”.
developmentTracks main. Bleeding-edge; what the project has been shipping historically.

Any other value returns invalid_release_channel from the PATCH endpoint.

Setting the channel

PATCH /api/v1/admin/settings with {"release_channel": "stable"}.

Effect on updates

  • The panel’s update card (Updates) reads the channel and offers upgrades that match.
  • The agent-side updater uses the same field when it pulls the panel or agent binary.
  • Switching from development to stable won’t downgrade you — the check simply waits for the next stable tag that’s newer than the current build.