Tuist CLI now uses three release channels: canary, release candidate, and stable. You can choose how much change you want to accept.
- Canary builds come from every CLI-related commit to main. Use them to preview the latest work; they are opt-in.
- Release candidates are cut from release branches for a slower soak. Use them to validate an upcoming stable line; they are opt-in.
- Stable releases are promoted deliberately after a candidate has soaked. They remain the default install and are recommended for production use.
The recommended stable line now moves slowly and only receives backported fixes, so upgrading no longer pulls in unrelated feature changes. You can pin a specific major.minor line to stay on a known-good release train.