Modify Getting Started to recommend the 5.10 toolchain temporarily. #76
Conversation
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
Due to a [Swift compiler bug](swiftlang/swift#69096) in the main branch, swift-testing cannot currently be used with it. Until that issue is resolved, we should direct developers to the 5.10 toolchain which is still a happy path.
grynspan
requested review from
SeanROlszewski,
briancroom,
dennisweissmann,
stmontgomery and
suzannaratcliff
as code owners
|
@swift-ci please test |
|
Thanks! Can you apply the same recommendation to |
grynspan
force-pushed
the
jgrynspan/recommend-510-toolchain
branch
from
833cc33 to
16f8d1e
Compare
|
@swift-ci please test |
stmontgomery
approved these changes
Oct 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to a Swift compiler bug in the main branch, swift-testing cannot currently be used with it. Until that issue is resolved, we should direct developers to the 5.10 toolchain which is still a happy path.
We can revert this change once the Swift compiler issue is resolved.