Setup Swift more Swiftly 🚀 (setup-swift 3.0) #710
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fwal
added
enhancement
Closed
Closed
fwal
changed the title
Collaborator
Author
|
Whoop - it's alive! |
dongjoon-hyun
added a commit
to apache/spark-connect-swift
that referenced
this pull request
Apr 29, 2025
### What changes were proposed in this pull request? This PR aims to upgrade `setup-swift` to `next` tag in order to test `setup-swift 3.0` dev version. - swift-actions/setup-swift#710 ### Why are the changes needed? To fix the flakiness issues during `Swift` installation on linux environment. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #94 from dongjoon-hyun/setup-swift-next. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
|
This is amazing @fwal 🚀. Thanks for driving this effort forward. |
|
This all sounds great!
Particularly excited by this, I assume that's looking to address #591? 😀 |
davidkoski
added a commit
to davidkoski/setup-swift
that referenced
this pull request
Jul 25, 2025
|
Any updates on this? |
1 task
4 tasks
# Conflicts: # .github/workflows/ci.yml # package-lock.json # src/linux-install.ts # src/swift-versions.ts # src/windows-install.ts
Collaborator
Author
|
This will be merged and released as a beta, you can use either |
Contributor
|
Should |
Collaborator
Author
|
Just pushed out a beta of v3 🎉 you can use that tag instead (that will also contain any future updates) @marcprux: |
Contributor
|
Great! You may still want to keep |
kkebo
added a commit
to kkebo/setup-swift
that referenced
this pull request
Dec 1, 2025
The functions `setupKeys` and `refreshKeys` have not been used since the transition to Swiftly in swift-actions#710. So the changes in swift-actions#772 are meaningless.
This was referenced Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an effort to rip out the old setup and replace it entirely with Swiftly - the preferred way to setup Swift going forward.
This brings several benefits like a unified way to setup Swift on all platforms and support for new Swift versions on day one 😅 and support for dev snapshots.
It will however be a breaking change as it will probably affect how version numbers is handled compared to the old version, stay tuned.
This will be a journey of trial-and-error...
General progress
Tip
This feature is work-in-progress but you can try it out using the
"next""v3" tag:swift-actions/setup-swift@nextswift-actions/setup-swift@v3Testing would be greatly appreciated ❤️
Decisions