Bump Swift version to 6.5#88900
Merged
Merged
Conversation
Member
Author
|
@swift-ci test |
Member
Author
|
Related package manager change: swiftlang/swift-package-manager#10032 swift-format appears to have automated this process (swiftlang/swift-format#1199) I expect we'll also need a similar version update in swift-testing (cc @grynspan), and possibly elsewhere (?) |
Contributor
|
Swift Testing has an issue in place to automate the process. |
glessard
approved these changes
May 7, 2026
shahmishal
approved these changes
May 7, 2026
shahmishal
reviewed
May 7, 2026
Co-authored-by: Mishal Shah <shahmishal@users.noreply.github.com>
Member
Author
|
@swift-ci smoke test |
Member
Author
|
Member
Author
|
@eeckstein |
Contributor
|
@swift-ci smoke test |
Contributor
|
@swift-ci smoke test macos |
Member
Author
|
@swift-ci smoke test |
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
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.
Now that we have opened
release/6.4.x, we need to be able to easily distinguish between toolchain builds produced frommainvs the new release branch, and we need to be able to introduce API and language/runtime features that targetmainonly.Bump the nominal Swift version to 6.5, and define an availability macro for
SwiftStdlib 6.5. Note that this is a provisional version number, serving as a technical placeholder that the project may decide to change. If that happens, then we can simply update these definitions as needed, similar to how Swift 5.11 got changed to Swift 6.0 during its development.