Skip to content

Take the static Linux SDK bundle version from the releases API - #302

Open
piercifani wants to merge 1 commit into
mainfrom
fix/static-sdk-bundle-version
Open

piercifani wants to merge 1 commit into
mainfrom
fix/static-sdk-bundle-version

Conversation

@piercifani

Copy link
Copy Markdown
Contributor

Why

SwiftSDKOpenAPI.fetchSDKs(sdkName: "static") builds the download URL with a hardcoded static-linux-0.0.1 bundle name. Since Swift 6.2.4, swift.org publishes the static SDK as static-linux-0.1.0, so the URLs for 6.2.4, 6.3.x and 6.4.x all return 404:

https://download.swift.org/swift-6.4.1-release/static-sdk/swift-6.4.1-RELEASE/swift-6.4.1-RELEASE_static-linux-0.0.1.artifactbundle.tar.gz → 404
https://download.swift.org/swift-6.4.1-release/static-sdk/swift-6.4.1-RELEASE/swift-6.4.1-RELEASE_static-linux-0.1.0.artifactbundle.tar.gz → 200

Change

releases.json already gives each platform's bundle version ("version": "0.1.0" on the static-sdk entry), so the URL now uses that. If the field is missing, it falls back to 0.0.1.

Testing

testParseSwiftToolchainAPI still checks the 6.2.3 (0.0.1) URL and now also checks the 6.4.1 (0.1.0) one. Both pass against the live API.

🤖 Generated with Claude Code

Swift 6.2.4 and later publish static-linux-0.1.0 bundles, so the hardcoded
static-linux-0.0.1 name produced 404 download URLs for them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cla-bot cla-bot Bot added the cla-signed label Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant