ci: add Swift example project compilation to CI pipeline#216
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
b0f2a05 to
77b1c1f
Compare
c822905 to
018c3b9
Compare
018c3b9 to
2cbb2d8
Compare
1968247 to
df05368
Compare
2cbb2d8 to
3fa7235
Compare
3fa7235 to
89b8958
Compare
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 89b895806e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| -project swift/Examples/IDKitSampleApp/IDKitSampleApp.xcodeproj \ | ||
| -scheme IDKitSampleApp \ | ||
| -sdk iphonesimulator \ | ||
| -destination "generic/platform=iOS" \ |
There was a problem hiding this comment.
Target iOS Simulator in simulator build step
The simulator build command uses -sdk iphonesimulator but still sets -destination "generic/platform=iOS", which is the device platform. xcodebuild treats iOS and iOS Simulator as separate destination platforms, so this mismatch can cause destination resolution errors and fail the swift-bindings job on every run that reaches this step. The destination here should be the simulator platform.
Useful? React with 👍 / 👎.
d44c998 to
8dde6c5
Compare

TL;DR
Upgrades CI to target macOS 26 / Xcode 26, adds a Swift sample app build step, and removes third-party Swift package dependencies.
What changed?
DEVELOPER_DIRenvironment variable is now set dynamically in a dedicated step to handle version strings containing hyphens (e.g.26.5-beta→26.5_beta).xcbeautifyfor cleaner output.IDKitSampleAppXcode project against the matrix-specified iOS SDK without code signing.BigInt,CryptoSwift, andswift-cryptohave been removed as Swift package dependencies fromPackage.swift, andPackage.resolvedhas been deleted entirely.How to test?
Push a branch and observe the CI workflow running against the updated macOS 26 matrix. Verify that the Swift tests pass, the sample app builds successfully for each SDK variant, and no dependency resolution errors occur due to the removed packages.
Why make this change?
The CI environment needed to be brought up to date with the latest Apple toolchain releases. Removing the third-party cryptography and big-integer dependencies reduces the package's external surface area, likely because that functionality is now handled internally (e.g. via the
idkitFFIbinary target or native framework APIs available in the newer SDKs).