Tuist CLI now ships through three release channels: canary, release candidate, and stable. Every CLI-touching commit to main publishes a canary prerelease (for example, 4.201.0-canary.N). When a minor is ready, a release candidate line is cut, soaked, and then promoted to stable. Stable becomes the recommended install that only receives backported fixes, so upgrading no longer pulls in unrelated features. Canary and RC builds are published as GitHub prereleases, so package managers such as Mise and Homebrew exclude them from default resolution. You can opt into a channel explicitly, for example: mise use tuist@latest for the latest stable, mise use tuist@4.200 to pin to a stable line, mise use tuist@4.201.0-rc.1 to soak a release candidate, or mise use tuist@4.201.0-canary.42 to试用a
Hive
CLI release channels (canary, RC, stable)
Published
Jun 16, 2026 · 08:59 UTC
Repository
tuist/tuist