-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Swift: Update to Swift 6.1.3 #20384
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
Swift: Update to Swift 6.1.3 #20384
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Swift toolchain from an earlier version to Swift 6.1.3, including both the prebuilt binaries and resource directories for macOS and Linux platforms.
- Updated Swift prebuilt binaries and resource directories for both macOS and Linux
- Added change notes documenting the Swift 6.1.3 update
- Updated binary checksums and file sizes to reflect the new Swift version
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
swift/third_party/resources/swift-prebuilt-macos.tar.zst | Updated macOS Swift prebuilt binary with new checksum and size |
swift/third_party/resources/swift-prebuilt-linux.tar.zst | Updated Linux Swift prebuilt binary with new checksum and size |
swift/third_party/resources/resource-dir-macos.zip | Updated macOS resource directory with new checksum and size |
swift/third_party/resources/resource-dir-linux.zip | Updated Linux resource directory with new checksum and size |
swift/ql/lib/change-notes/2025-09-08-swift-6.1.3.md | Added change notes documenting the Swift 6.1.3 update |
Yep, 4/15 projects failing to build is concerning, though the errors are in the "before" runs as much as the "after" so very likely unrelated to these changes. I see that runs 1 and 2 are worse. Do you have any idea what's going on? |
For MovieSwiftUI, bark, and Tofu it seems to the connection to the runner was lost. This seems to happen quite a lot nowadays, also integration tests. This looks like an infrastructure problem. For Swiftmazing it looks like the the used version of |
You want to ignore the DCA runs marked |
So this needs fixing in the DCA config somehow? Let me know if I can help with that. |
Yes, I opened an internal issue for this. |
Great, thanks! |
The DCA experiment (
__3
) is a bit messy, but doesn't give me reason for concern.