CLI 4.201.0-canary.12

The Tuist CLI now ships through three release channels: canary, release candidate, and stable. Canary builds publish on every relevant commit, RCs soak on a release branch, and stable releases are promoted only after soaking. This gives you a slower-moving recommended install while keeping per-commit builds available for early adopters.
The module cache now supports static and dynamic library products, not just frameworks. Cached libraries are produced as XCFrameworks and restored with the Swift module and public header metadata needed to compile against them.

tuist inspect dependencies now detects implicit imports that come from Swift Package Manager binary targets backed by XCFrameworks.
tuist cache warm no longer parses Xcode activity logs to estimate per-target build durations, removing a failure point when logs were missing or unparseable.
Long Bazel builds against the Tuist remote cache no longer hit waves of UNAUTHENTICATED errors when short-lived access tokens expire. The credential helper refreshes proactively within a 60-second safety margin.

Packages that use SwiftPM’s newer warning-control APIs, such as swift-dependencies 1.13.0, now load successfully.
The SwifterPM-backed SwiftPM integration now skips __MACOSX shadow bundles from Finder-zipped binary artifacts, streams swift package resolve output, and uses SwiftPM’s artifact scratch path for restores.

Suite-granularity sharding now selects Swift Testing suites by passing -only-testing to xcodebuild instead of relying on OnlyTestIdentifiers, which silently skipped Swift Testing tests.
When you run sharded tests with a test plan, Tuist now uses that plan to resolve the simulator destination, so schemes with multiple test plans get a concrete destination instead of a platform-only fallback.

Graph processing now uses iterative traversal instead of recursion, preventing stack overflow crashes on very large dependency graphs.