История изменений

We're introducing two new features to make managing and distributing previews even better.

Preview tracks

You can now organize your previews into named tracks like beta, nightly, or internal:

Tracks make it easy to group previews by purpose and filter them in the dashboard.

Tuist SDK

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.

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.

You can now authenticate with Tuist in CI environments using OpenID Connect (OIDC) tokens. This eliminates the need to manage long-lived secrets - just connect your GitHub repository to your Tuist project and run tuist auth login in your CI workflow.

OIDC authentication is currently supported on GitHub Actions, CircleCI, and Bitrise. See the CI integration documentation for setup instructions.

You can now create fine-grained account tokens with specific scopes and project access. Unlike project tokens, account tokens let you control exactly which operations the token can perform and which projects it can access.

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.

In details of generate and cache runs, you can now expand each module to see its subhashes and metadata, which is especially useful when debugging inconsisten hashes across environments.

When signing up, you can now choose your username instead of the username being generated for you:

The dashboard now includes a new "Tests" page that shows a summary of your tests – such as your average test duration, recent test runs, or your slowest test cases.

We're adding a new "Test Cases" page that shows a summary of your test cases, including your individual slowest test cases. Additionally, you can see a history of runs for each individual test case in the test case detail page.

When viewing test details, we link to the corresponding CI run when the test was executed by a supported CI platform.

When testing, we'll now show a link to the corresponding build and vice versa.

Track your test performance with the new Test Insights. Monitor test durations, identify slow tests, and quickly debug failed CI runs. See documentation to get started.