Deployment
Version compatibility
TurboPanel publishes artifacts on channels promoted from trunk → canary → rc → release. Control plane and daemon versions must stay within the supported matrix for your channel.
Channels
| Channel | Audience | Notes |
|---|---|---|
trunk | Contributors | Moves daily; not for production |
canary | Early adopters | Pre-release validation |
rc | Release candidates | Short-lived before release |
release | Production | Security fixes and stable upgrades |
Manifests are generated by the daemon release tooling (generate-channel-manifest.ts) and published to the CDN installer path.
Pairing rules
| Control plane | Daemon | UI |
|---|---|---|
| Same major channel family | Match installer manifest min control plane field | Bundled with control plane deploy (static export) or Workers assets (HA) |
Rule of thumb: upgrade the control plane first, then roll daemons fleet-wide. Mixed trunk control plane + release daemons (or the reverse) is unsupported outside active development.
Check versions
| Surface | How |
|---|---|
| Daemon | turbopaneld --version or /opt/turbopanel/bin/turbopaneld |
| Control plane (Deno) | GET /api/health + build info in logs |
| Control plane (Workers) | Cloudflare deployment tag / release notes |
| UI | Static export stamp in /opt/turbopanel/share/ui or Expo dev server (development only) |
Breaking changes
Breaking API or enrollment changes are called out in:
- Changelog
- GitHub Releases
- Release notes for
turbopaneld
Related
Edit on GitHub
Last updated on