The tooltip is available in both the Test History tab and the compact history section on the test case overview.
Marked as flaky, Unmarked as flaky, or state transitions to Enabled / Muted / Skipped — and the configured actions fire right away. The common shape: someone manually marks a flaky test, the automation immediately mutes it and pings Slack. Each automation-driven change also lands on the test case timeline attributed back to the rule that triggered it, so you can always see which automation moved a test and why.
30d, or Rolling window to evaluate over the last N runs of each test case — useful when test volume varies day-to-day and a fixed time window over- or under-reacts to recent activity. The same dropdown is wired into Recovery so you can wait either for X days or for N new runs without a re-trigger before recovery actions fire.
Greater or equal, Greater than, Less than, and Less or equal. Pair it with a "Less than" comparison and an Unmark as flaky action to clean up stale flaky labels — including ones set manually or by an automation you've since removed — without touching tests that are still flaking.
SCIM provisioning works alongside SSO: SCIM manages membership lifecycle, while SSO controls sign-in. Deprovisioned members are removed from the organization, preserving their user record and historical work without disabling access to other Tuist organizations.
GitHub Apps are scoped to a single GitHub instance, so the github.com Tuist App can't be installed on a GHES instance — every customer registers their own copy. The credentials Tuist receives from the manifest exchange are stored encrypted per-installation. No env vars or Tuist server configuration changes are needed.
-skip-testing and the Gradle plugin filters with excludeTestsMatching). Pick the mode from the test case dropdown, filter by it on the Quarantined Tests page, or have an automation set it for you.
HTTPS_PROXY or HTTP_PROXY is set in the environment, Tuist now automatically routes the HTTP connections it manages (cache, previews, analytics, registry access, and the calls the Gradle plugin makes back to Tuist services) through that proxy. Nothing to configure: the CLI and Gradle plugin pick up the variable and use it. ]]>@Test(arguments:)). Each argument variant is tracked individually with its own status, failures, and attachments, giving you per-argument visibility into what passed and what failed.
tuist setup insights to enable metric collection. Gradle builds collect metrics automatically through the plugin.
assembleRelease, connectedAndroidTest), making it easy to distinguish between different build types in CI environments with multiple builds.
This first release includes:
/mcp with proper bearer challenges.list_projectslist_test_cases (with optional flaky filter)get_test_caseget_test_runget_test_case_runfix_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.
]]>.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.
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:
xcodebuild test $(tuist test case list --skip-testing).
You can now organize your previews into named tracks like beta, nightly, or internal:
tuist share App --track beta
Tracks make it easy to group previews by purpose and filter them in the dashboard.
The new Tuist SDK enables your app to detect when a newer preview version is available and notify users - keeping testers on the latest build.
import TuistSDK
struct MyApp: App {
var body: some Scene {
WindowGroup {
ContentView()
.task {
TuistSDK(
fullHandle: "myorg/myapp",
apiKey: "your-api-key"
)
.monitorPreviewUpdates()
}
}
}
}
The SDK checks for updates within the same preview track. When you share with --track beta, the SDK notifies about newer builds on that track. Update checking is automatically disabled on simulators and App Store builds.
See the Previews documentation for more details.
tuist inspect dependencies command that combines implicit and redundant dependency checks in a single invocation. This makes it ~2x faster by loading your project graph only once.
# Run both checks (default)
tuist inspect dependencies
# Run specific checks
tuist inspect dependencies --only implicit
tuist inspect dependencies --only redundant
The previous tuist inspect implicit-imports and tuist inspect redundant-imports commands still work but are deprecated in favor of the new unified command.
tuist auth login in your CI workflow.
name: Build
on: [push]
permissions:
id-token: write
contents: read
jobs:
build:
runs-on: macos-latest
steps:
- uses: actions/checkout@v4
- uses: jdx/mise-action@v2
- run: tuist auth login
- run: tuist generate
OIDC authentication is currently supported on GitHub Actions, CircleCI, and Bitrise. See the CI integration documentation for setup instructions.
]]>tuist account tokens create my-account --scopes project:cache:read project:cache:write --name ci-cache-token --expires 1y
Account tokens support various scopes covering cache, previews, builds, tests, bundles, registry, and account management. You can also set expiration dates and restrict tokens to specific projects within an account.
]]>
only-external (default), all-possible, or none, or define your own custom profiles in Tuist Config.
Read more about cache profiles in our documentation.
tuist test:
tuist test --skip-ui-tests
Now, we're bringing the some convenience flag for unit tests:
tuist test --skip-unit-tests
This way, you can easily have separate CI pipelines for UI and unit tests, such as when you don't want to run your UI tests for every PR but instead nightly.
]]>Read more about it in our blog post.
However, each bundle type can have a slightly different bundle size. While we recommend to primarily use the .ipa bundle type as the install and download size is the most accurate representation of what users will experience, the other types might be useful to recognize a spike in the bundle size early.
To streamline seeing a graph for a specific bundle type, we've added the option to filter by .ipa, .app, or .xcarchive:
This feature supports:
# List bundles in the current project
tuist bundle list
# List bundles in a specific project
tuist bundle list --project account/project
# Output bundle list as JSON for scripting
tuist bundle list --json
# View detailed information about a specific bundle
tuist bundle show {id}
These commands handle authentication and session management automatically, making it easy to integrate bundle operations into your CI/CD pipelines and custom automation workflows.
]]>Add this setting to your Tuist.swift configuration:
// Tuist.swift
import ProjectDescription
let tuist = Tuist(
project: .tuist(
cacheOptions: .options(
keepSourceTargets: true
)
)
)
When enabled, Tuist generates:
-Cached scheme containing all source targets isolated from the main dependency graphThis allows you to switch between optimized binary builds and full source access without regenerating your project.
Note: These source targets are for inspection and debugging only. If you modify their sources, you'll need to regenerate your project to reconcile the changes with the dependency graph.
]]>.pbxproj files. While we initially postponed support since these conflicts weren't frequent in our workflow, user feedback revealed another compelling benefit: buildable folders eliminate the need to regenerate projects when files are added outside of Xcode's UI—particularly valuable for automated agents and CI/CD pipelines.
Based on this feedback, we've now added support for buildable folders. If you're currently using Target.sources and Target.resources, you can migrate to the new Target.buildableFolders property to define buildable folders for your targets.
Note: Xcode's synchronized groups (the underlying implementation of buildable folders) support "exceptions"—files or folders that can be excluded from synchronization. While we don't support exceptions yet, we'll add this feature based on user demand.
]]>Previously, releasing new versions of Tuist required manual intervention from maintainers. This created bottlenecks and delays in getting new features and fixes to users. Now, we've implemented an automated release pipeline that:
Each component (CLI, Server, and macOS app) now has its own release pipeline that:
feat(cli): for CLI changes, feat(app): for app changes)We're using git cliff with custom configurations for each component:
(cli) scope or no scope(server) scope(app) scopeThe pipelines run on GitHub Actions and handle everything from version bumping to updating package managers like Homebrew.
This automation represents our commitment to making Tuist more accessible and reducing barriers for both contributors and users. We believe that great developer tools should be easy to contribute to and quick to deliver value.
]]>To achieve this, we’ve introduced Noora{:target="_blank"}—a design system for building CLIs in Swift. This Swift package provides themable components designed specifically for CLI interfaces. While the current selection of components is limited, we plan to gradually expand it by extracting more components from our work at Tuist.
If you’re building a CLI in Swift, we encourage you to explore the documentation{:target="_blank"}. We’d love to hear your feedback and welcome contributions to make Noora even better. If there’s a specific component you need, feel free to open an issue or submit a PR!
Transitioning from Tuist Air to Tuist Pro is now simpler—just add a payment method, and you'll only be charged for usage exceeding the defined thresholds. To make everything clearer, we've included a table outlining how the usage of various features is measured.
Looking ahead, we plan to provide examples, an estimation calculator, and tools to help you set usage limits, so you can stay within your budget and enjoy peace of mind.
]]>As part of this work we've also:
The design of the website has been done by Guinda Studio and it's publicly available.
]]>