-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[5.10] Fix non-tarballed SDK installation with remote URL (#7312) #7321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.10] Fix non-tarballed SDK installation with remote URL (#7312) #7321
Conversation
### Motivation: 4714ea9 introduced a regression where non-tarball SDKs could not be installed from a remote URL due to the wrong assumption that the downloaded file would always be a tarball. This issue exists in 5.10 release branch, so will cherry-pick after merging this PR. ### Modifications: This commit fixes the issue by checking the file extension part of the URL for every supported archive format, then falling back to the tarball format if no supported extension is found. ### Result: Non-tarball SDK artifact bundles can be installed from remote URL.
@swift-ci Please test |
@kateinoigakukun would you mind adding a filled in form to the PR description with Explanation/Scope/Risk/Testing etc fields matching recent 5.10 PRs, like this one for example? #7308 |
Gentle ping :) |
Unfortunately, it doesn't look this will make it in time for 5.10.0 as the bar for that is very high. It may still be eligible for subsequent patch 5.10.x releases if those happen, so I'll keep this PR open for now. |
@swift-ci test |
We need to hold off merging this unfortunately for a bit more time. There are infrastructure changes requires for this to land correctly post 5.10.0
🍒 #7312
swift experimental-sdk
command, which is still experimental. Also doesn't impact other binaries or SwiftPM clients/libraries.