What changed
Updated the Tuist CLI dependency on tuist/swifterpm from 0.8.1 to 0.8.3.
Added LD_RUNPATH_SEARCH_PATHS for SwiftPM prebuilt library search paths so generated targets can load the prebuilt libraries at runtime.
Why
tuist/swifterpm released the dependency-resolution and workspace-state fixes Tuist needs across 0.8.2 and 0.8.3:
0.8.2 refreshes stale binary artifact archives.0.8.3 preserves SwiftPM prebuilts in workspace state and sanitizes the prebuilt path fields.
The reproduced tuist install failure was no versions found for apple.swift-protobuf matching constraints; tuist install now resolves apple.swift-protobuf successfully with swifterpm 0.8.3.
I intentionally did not keep the Tuist-side path-sanitization fallback from the merged worktree because swifterpm 0.8.3 now owns that before writing workspace-state.json.
0.8.4 is the newest swifterpm tag, but it cannot currently be consumed by Tuist as a stable Swift package version because its manifest depends on swiftlang/swift-package-manager by revision. swift package resolve --replace-scm-with-registry rejects that combination for an exact version dependency, so this PR uses the latest swifterpm release that resolves in Tuist.
Impact
Tuist consumes the released swifterpm fixes through the exact package pin and resolved lockfile revision. tuist install can resolve and restore registry packages again, including apple.swift-protobuf. SwiftPM prebuilt targets also get a runtime search path for their prebuilt libraries.
Validation
swift package resolve --replace-scm-with-registrytuist installtuist generate tuist ProjectDescription --no-openxcodebuild build -workspace Tuist.xcworkspace -scheme tuist CODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY=""tuist generate TuistLoaderTests --no-openxcodebuild test -workspace Tuist.xcworkspace -scheme TuistUnitTests -only-testing TuistLoaderTests/PackageInfoMapperTests CODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY=""
T
