Agent Release Trains
Overview
A release train is the version channel your Self-Managed Agents follow. Different partners want different amounts of risk, so Liongard lets you choose how quickly your Agents receive new Agent versions.
Requires Agent 5.5.0Release train selection appears in the Liongard UI starting September 16, 2026, but only Agents running 5.5.0 or later can act on it. If your Agents are on an earlier version, this setting has no effect until they update. See Agent Auto-updating for the upgrade path.
The Trains
Four release trains exist. You can select three of them; the fourth, Canary, is assigned by Liongard.
| Train | UI Label | Who Sets It | What It Is |
|---|---|---|---|
| Early Access | Early Access (EAP) | Partner | New features first. May be less stable. Best for test Environments. |
| Stable | Stable | Partner | The current general availability build. |
| Long-Term Support | Long-Term Support (LTS) | Partner | The previous proven Stable build. This is the default when nothing is set. |
| Canary | Canary (managed by Liongard) | Liongard only | Assigned by Liongard when working directly with a partner to validate a build. You cannot select it yourself. |
What You Get If You Do Nothing
If you do not set a release train, your Agents follow Long-Term Support (LTS). This is the most conservative option. If you want current builds, choose Stable or Early Access instead.
How to Set It
Organization-wide: Go to Company Settings > Agents and set the RELEASE TRAIN field. Requires Admin group membership and the Edit Agent permission.
Per Agent: Go to Admin > Agents, click the Agent's name, and set the RELEASE TRAIN field. Requires the Edit Agent permission. Not shown for On-Demand (Liongard-Managed) Agents.
A release train set on an individual Agent overrides the organization's release train.
No Bulk ActionRelease Train cannot be set in bulk. Set it one Agent at a time from the Agent Details screen.
How a Version Gets Chosen
- If the individual Agent has a release train set, that wins.
- Otherwise, the organization's release train applies.
- If neither is set, the Agent follows Long-Term Support (LTS).
Each train includes itself plus every more conservative train below it, and the highest version number available across that set wins. The order, most current to most conservative, is Early Access, Stable, Long-Term Support.
For example, if you pick Early Access but there is no Early Access build newer than the current Stable build, your Agents stay where they are. That is expected, not a bug.
About Canary
Canary is assigned directly by Liongard when working with a partner to validate a build. You cannot self-select it. If you want current builds without waiting for a wider release, Early Access is the self-serve option.
Related
Updated about 3 hours ago