Forage

Offer customers an opt-in way to pin a runner to their own workflow run, so a runner Tuist starts for their job cannot be taken by a different job. This is the mitigation [RunsOn d…

Tuist.Registry.Swift.ReleaseWorker fetches every submodule with --depth 1. When a submodule is pinned to a commit that is not reachable from a ref tip — a routine situation, si…

Since #10256 (2026-04-13), a package whose tag carries a .gitmodules is routed away from GitHub’s zipball and into a full git clone with --init --recursive. The entire submod…

When the CLI’s credentials file holds an account-type token, the accompanying refresh token is discarded at parse time and never used. Once the access token expires the CLI keeps p…

Found while investigating the Could not find Package.swift in this directory or any of its parent directories reports (fixed diagnostically in #12224). This is a separate defect …

On Tuist versions up to 4.202.x, we are using a private, authenticated registry endpoint via the following (simplified) steps:

tuist install fails to restore Swift packages hosted on git servers that reject shallow fetches — in our case the generated SDKs on buf.build (`https://buf.build/gen/swift/gi…

When a scheme switches from a path-based .xctestplan to a generated test plan, plan-level test settings cannot be represented and are silently absent from the generated file.

Tuist generates each SPM package in a workspace as its own Xcode project, and target dependencies inside a project become real dependency edges in the build description. But depend…

Deferred hardening from #11788 (per-account macOS runner cache volumes, spec #76). Tracking this review thread; …