Server 1.204.0

Tuist Server 1.204.0 improves runner management, flaky-test alerting, and cache downloads.

Runner Profiles

• You can now create account-scoped Runner Profiles for Linux runners. Each profile bundles a vCPU and RAM configuration behind a name, and you can reference it from GitHub Actions with runs-on: tuist-<name>. Updating a profile’s resources automatically applies to every workflow that uses it, so you no longer need to edit workflow files to change runner specs.

Testing & alerts

• Flaky-test alerts now only trigger for test cases that have at least one successful, non-flaky run on the project’s default branch. New tests introduced in a pull request will no longer be auto-muted before they have been validated on the default branch.

Cache

• Restored the x-tuist-signature header on central Tuist cache responses when a cache hash is present. This fixes cache downloads that failed with “Invalid or missing signature from cache server” on clients that still verify cache response signatures.

Infrastructure

• Kura cache endpoints are now regional only. Account-level Kura endpoints have been removed and migrated to regional endpoints.