swiftlang / swiftlang/github-workflows
Android/WASM workflows can build with mismatched toolchain + SDK versions
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 115
- Forks
- 57
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
It appears that in some cases it's possible for the Android/WASM swift package test workflows to build against an Android/WASM SDK that does not match our toolchain version. For example, see https://github.com/swiftlang/swift-foundation/actions/runs/23912627888/job/69738273919?pr=1871:
** Found latest main wasm-sdk snapshot: swift-DEVELOPMENT-SNAPSHOT-2026-04-01-a
** Found wasm-sdk checksum: 5ae95d926686...
** Found wasm-sdk download filename: swift-DEVELOPMENT-SNAPSHOT-2026-04-01-a_wasm.artifactbundle.tar.gz
** ✅ Found Swift snapshot tag in /.swift_tag: swift-DEVELOPMENT-SNAPSHOT-2026-03-16-a
** Installing Swift toolchain to match Wasm Swift SDK snapshot: swift-DEVELOPMENT-SNAPSHOT-2026-04-01-a
This seems to be resulting in build failures due to a "bad" SDK when building swift-foundation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Android and WASM Swift package test workflows and the /.swift_tag value, then inspect the linked workflow run for how the SDK and toolchain versions are selected. Done means the workflows consistently use matching Android/WASM SDK and Swift toolchain versions and the swift-foundation build no longer fails from a mismatched SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, github-actions, swift, wasm
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100