This canary CLI release introduces release channels and tightens cache warming and SwiftPM integration.
Release channels
The Tuist CLI now ships through three channels: canary, release candidate, and stable. Canary builds are published from every CLI change on main and are opt-in. A release candidate line is cut to a release branch, soaks, and is then promoted to stable. Stable remains the default recommended install, so you can upgrade to a slow-moving release line while early adopters test per-commit canaries.
Cache warming
Cache warming no longer copies and parses .xcactivitylog files to infer per-target build times. That timing metadata was not surfaced in the product, and missing or unparseable activity logs could fail the cache warm step even though the binary artifacts had built successfully. Binaries are still built, packaged, and uploaded as before.
SwiftPM dependency resolution
The bundled SwifterPM integration is updated to skip __MACOSX shadow bundles when extracting binary artifacts. This resolves generation failures such as “doesn’t contain an Info.plist” for Finder-zipped artifacts. SwiftPM resolve output is also streamed, so progress appears during resolution instead of looking stalled.