Tuist 4.201.0 is now stable, and 4.202 is ready for RC testing
We’ve promoted 4.201.0 to stable. This is the first stable release after introducing release lines, so latest now points at the version we recommend most teams use by default.
This release includes the recent module cache work we’ve been iterating on, plus a set of SwiftPM, testing, and generation fixes that should make day-to-day use of Tuist more predictable.
What’s new in 4.201
4.201.0 includes support for library products in the module cache, which expands the set of package products Tuist can cache.
It also includes several fixes around prebuilt and SwiftPM dependencies, especially static Objective-C XCFrameworks with custom module maps and nested header layouts. These changes make cached dependency graphs more reliable when those frameworks are consumed indirectly through other modules.
We also fixed an issue where tuist cache warm and tuist generate could compute different hashes for the same target, causing a warmed binary to be missed during generation.
Other notable improvements include:
- Better handling of SwiftPM binary dependencies (#10918) and static library artifact bundles (#11325)
- Support for SwiftPM warning control settings (#11326)
- Package documentation module import fixes (#11135)
- Proto files treated as sources (#11211)
- More reliable suite-granularity test sharding (#11329, #11331)
- Hostless tests isolated in workspace schemes (#11225)
- Improved framework search path handling (#11382)
- Several smaller cache, generation, and build-run reporting fixes, including generated module map timestamp preservation (#11351), external resource bundle handling in cached frameworks (#11257), and scheme test configuration reporting in build runs (#11378)
You can install the stable release with:
mise use tuist@latest
Help us test the next RC
We’ve also published 4.202.0-rc.1, the first release candidate for the next stable line.
This RC includes more SwiftPM, module cache, generation, and test-sharding improvements. We’d love feedback from teams running larger projects or heavier caching setups before we promote it to stable.
You can try it with:
mise use [email protected]