This canary release improves module caching, SwiftPM dependency handling, and the CLI’s release distribution.
Features
- You can now cache static and dynamic library products in the module cache, alongside frameworks. Cached library XCFrameworks keep public headers and Swift module directories intact, so mixed framework/library projects reuse binaries across local and CI builds.
- The Tuist CLI now ships through three release channels: canary, release candidate, and stable. Stable releases only land after a deliberate soak period, so the recommended install moves more slowly; canary builds stay opt-in.
Bug Fixes
- The Bazel credential-helper refreshes access tokens 60 seconds before they expire, preventing bursts of UNAUTHENTICATED errors during long remote-cache builds.
- Suite-level test sharding now passes
xcodebuild -only-testingidentifiers, so Swift Testing suites actually run instead of reporting success with zero tests. - You can now load SwiftPM packages that use newer warning-control APIs (for example, swift-dependencies 1.13.0), and Tuist maps those warning settings into the generated Xcode build settings.
- SwiftPM artifact extraction strips
__MACOSXshadow bundles from Finder-zipped archives, fixing generation failures with packages like Plaid LinkKit;swift package resolveprogress is now streamed; and restores use SwiftPM’s artifact scratch path. - Tuist no longer tracks how long individual cache targets take to build.