Block pull requests when your app's bundle size grows beyond a configured limit. Tuist automatically creates GitHub Check Runs that compare the install or download size against a baseline branch. If the threshold is exceeded, you can accept the increase directly from the GitHub UI. Learn more in the bundle insights documentation.
See attachments associated with a given test case run directly in the dashboard to understand why your tests might have failed as quickly as possible.
You can now click on any test case run to open a dedicated detail page with everything you need to understand what happened in that run.
Tuist now supports the Model Context Protocol (MCP) over HTTP so coding agents can authenticate and interact with your Tuist data directly.
This first release includes:
/mcp with proper bearer challenges. list_projects list_test_cases (with optional flaky filter) get_test_case get_test_run get_test_case_run fix_flaky_test) that guides agents through diagnosing and fixing flaky tests. This gives agents enough context and tooling to inspect flaky tests and drill down into run-level failure details from Tuist.
When a test crashes (e.g. force-unwrap of nil), Tuist now extracts the crash log from the xcresult bundle, parses it, and surfaces the stack trace directly in the test run dashboard. Each failure card shows the exception type, signal, and formatted crash thread frames so you can diagnose crashes without leaving your browser. The full .ips crash log is also available for download.
Additionally, the crash report is available in the CLI (tuist test case show <test-case-run-id>), which makes the crash report available to agents when for example fixing flaky tests.
Get notified via Slack when your app's bundle size increases significantly. Configure alert rules to monitor install or download size changes on a specific branch, and catch unexpected size regressions before they reach your users.
You can now attach custom metadata to your builds using environment variables. This includes both tags for categorization and key-value pairs for additional context like ticket numbers or CI runner information.
Use TUIST_BUILD_TAGS or TUIST_BUILD_TAG_* for tags, and TUIST_BUILD_VALUE_* for key-value pairs.
Filter your build analytics by tag in the dashboard:
View tags and custom values in the build detail page:
View all quarantined tests in your project at a glance. The new page shows analytics tracking the number of quarantined tests over time, and a searchable table with filtering options.
Track the complete history of state changes for each test case. The new Test History tab shows a timeline of events including when a test was first seen, when it was marked or unmarked as flaky, and when it was quarantined or unquarantined. Each event shows who made the change - whether it was done manually by a team member or automatically by Tuist.
Quarantine flaky tests to prevent them from blocking your CI pipeline. Tests can be automatically quarantined when marked as flaky, or manually quarantined from the test case detail page. Skip quarantined tests by running xcodebuild test $(tuist test case list --skip-testing).
