Tuist CLI now distributes releases through three channels: canary, release candidate, and stable. Canary builds are cut from every commit to main, release candidates soak on a dedicated branch before promotion, and stable releases become the recommended install. This separates new features from backported fixes, so tuist@latest no longer advances on every commit and only receives patch updates.
- Opt into canary builds to preview the latest changes before they reach stable.
- Pin to
tuist@latestor a specificmajor.minorline to stay on a slower, patch-only cadence. - The latest-release lookup now excludes prereleases, so canary and RC versions are never advertised as the recommended install.