Forage

• Exposes the hidden tuist test run subcommand in the tuist help test subcommand list.

#11558 made suite-granularity shard plans correct by recovering modules that were missing from the initial xcodebuild -enumerate-tests output. That recovery still depended on sim…

A silent kernel lockup on a single-box bare-metal Kura region (Dedibox / OVH / Scaleway Elastic Metal) leaves its Node NotReady indefinitely, which silently wedges every …

Cuts the production main CNPG cluster (tuist-tuist-pg, 3 instances) over from in-tree barmanObjectStore to the Barman Cloud Plugin, using **`primaryUpdateMethod: restar…

Fixes the self-hosting guides where they were inaccurate/out-of-date, and removes the setup friction that surfaced while helping a customer stand up a standalone node: on a self-ho…

Follow-up fixes surfaced while investigating remote xcresult processing, after #11602 landed the migrate-time processor grants + the webhook_endpoints fix. Four fixes across thre…

Tuist.Shards.resolve_units/4 for suite granularity now pattern-matches a non-empty list ([_ | _] = suites) before using client-supplied test_suites, so a present-but-nil va…

A finished test run could stay stuck on the “processing” spinner in the web UI even though ClickHouse already showed status=success — the run looked perpetually unprocessed u…

Requested on Slack: at the end of a tuist cache warm run, print how many targets were served from the remote cache, so setup/CI logs can report the remote hit rate without a se…

When mapping SwiftPM packages, Tuist no longer copies a package-wide PRODUCT_BUNDLE_IDENTIFIER onto each generated target. Every other base setting from `packageSettings.baseSett…