Skip to content

Bump swift-sdk to 0.12 to fix build under Swift 6.3#3

Open
arihantdaga wants to merge 1 commit into
jsflax:mainfrom
arihantdaga:fix/swift-sdk-0.12-concurrency
Open

Bump swift-sdk to 0.12 to fix build under Swift 6.3#3
arihantdaga wants to merge 1 commit into
jsflax:mainfrom
arihantdaga:fix/swift-sdk-0.12-concurrency

Conversation

@arihantdaga

Copy link
Copy Markdown

Why

swift build/swift run fails on the Swift 6.3 toolchain. The pinned swift-sdk 0.10.2 captures a var across an actor boundary in NetworkTransport, which 6.3's strict-concurrency checker now rejects as a hard error (#SendingRisksDataRace) rather than a warning. The build dies in the dependency before our code compiles.

What

  • Bump swift-sdk to 0.12 — the race is fixed upstream (the flag is wrapped in a @MainActor reference type).
  • Adapt the one Tool.Content.text destructuring site to its new tuple-shaped associated values (0.12 API change).
  • Raise the manifest floor from: "0.12.0" so the lockfile, manifest, and source all agree on the required SDK.

No toolchain or platform floor change: swift-sdk 0.12 keeps the same swift-tools-version:6.1 and macOS 13 minimum as 0.10. The project already required swift-tools-version: 6.2.

Testing

swift build -c release is green and produces the EngramVisualizer binary. Builds on both Swift 6.2 and 6.3 (6.3 was previously broken).

swift-sdk 0.10.2 fails to compile on the Swift 6.3 toolchain — its
NetworkTransport captures a var across an actor boundary, which 6.3's
strict-concurrency checker now treats as a hard error. 0.12 fixes the
race upstream. Adapts the one Tool.Content.text destructuring site to
the new tuple-shaped API and raises the manifest floor to match.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant