You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Swift SDK that contain pre-built stdlib and platform required libraries, the versions of the Swift compiler in the host toolchain and the one used to build libraries in the Swift SDK must be exactly the same.
For SDKs built from nightly snapshot toolchain, users need to use a specific snapshot version of toolchain, but currently there is no easy way to find the corresponding nightly docker image because all nightly images are tagged as the same name.
If we can push nightly images with alternative unique suffix like git tag name (e.g. swift-5.10-DEVELOPMENT-SNAPSHOT-2024-03-02-a), it would help nightly Swift SDK users a lot.
If we can push nightly images with alternative unique suffix like git tag name (e.g. swift-5.10-DEVELOPMENT-SNAPSHOT-2024-03-02-a), it would help nightly Swift SDK users a lot.
It would be very helpful if that were to happen.
However, if there are the CI job logs that show the Swift toolchain version and the hash of the image that was pushed, that should be sufficient. I didn't know where to find the logs. I've found it. (nightly-6.0, nightly-main)
When using Swift SDK that contain pre-built stdlib and platform required libraries, the versions of the Swift compiler in the host toolchain and the one used to build libraries in the Swift SDK must be exactly the same.
For SDKs built from nightly snapshot toolchain, users need to use a specific snapshot version of toolchain, but currently there is no easy way to find the corresponding nightly docker image because all nightly images are tagged as the same name.
If we can push nightly images with alternative unique suffix like git tag name (e.g. swift-5.10-DEVELOPMENT-SNAPSHOT-2024-03-02-a), it would help nightly Swift SDK users a lot.
(Original conversation: kkebo/swift-syntax#7 (comment))
The text was updated successfully, but these errors were encountered: