Merged
Conversation
Motivation * Nightly CI was failing with a checksum mismatch because the static Linux SDK filename was hardcoded to `_static-linux-0.0.1`, but the SDK has since been released as `0.1.0` with a different checksum. * The swift.org releases API returns a `version` field alongside the checksum for the `static-sdk` platform, so the version can be resolved dynamically. Modifications * Added `extract_static_sdk_version()` to read the `version` field from the releases API response. * In the `version` install path, override `sdk_suffix` with the API-provided version rather than the hardcoded `0.0.1`. Result * The correct SDK filename (`_static-linux-0.1.0`) is now resolved and hopefully will continue to work for future version bumps.
This reverts commit 732e060.
FranzBusch
approved these changes
Mar 3, 2026
Contributor
Author
|
The Benchmarks failure looks like a bug in package-benchmark on Swift 6.0 |
Member
|
I guess it is because of the new release https://github.com/ordo-one/package-benchmark/releases. @hassila are you aware of this potential regression in 6.0? |
Contributor
|
@supersonicbyte could you have a look please - seems the trait support regressed 6.0 😞 |
Contributor
looking into it! |
Contributor
Author
Member
|
Merging over the benchmark failure because that is unrelated to this PR. |
Contributor
|
Sorry for the regression, should be fixed with: https://github.com/ordo-one/package-benchmark/releases/tag/1.31.0. Let me know how it goes. |
Member
|
@supersonicbyte Thank you for the quick fix! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fix static Linux SDK version hardcoding
Motivation
Linux SDK filename was hardcoded to
_static-linux-0.0.1, but theSDK has since been released as
0.1.0with a different checksum.versionfield alongsidethe checksum for the
static-sdkplatform, so the version can beresolved dynamically.
Modifications
extract_static_sdk_version()to read theversionfield fromthe releases API response.
versioninstall path, overridesdk_suffixwith theAPI-provided version rather than the hardcoded
0.0.1.Result
_static-linux-0.1.0) is now resolvedand hopefully will continue to work for future version bumps.