Development open for Swift 6.1.1 for Linux and Windows

Development Announcements
1

We are happy to announce the opening of the development phase for Swift 6.1.1 for Linux and Windows.

  • Merge window open: 8th April 2025
  • Merge window close: 25th April 2025
  • Planned release: End of April 2025
  • Release manager: @mishal_shah (shahmishal on GitHub)
  • Process documentation
  • Changes for Swift version 6.1.1 should be made on the release/6.1.1 branch, which was created from the swift-6.1-RELEASE tag.
5 Likes
2

Hi Mishal,

So trying to understand - we have one fix we are anxiously waiting for (which blocks our migration to 6.1) which was cherry-picked to the 6.1 branch, but is not part of the 6.1.1 branch now that we checked.

According to the process documentation, it says:

The changes for the dot release must be only focus on non-darwin platforms only

So as the bug fix abov is relevant for all platforms, we aren't allowed to open a PR for it to be included due to this stipulation.

What is the interaction between the 6.1 branch and the 6.1.x branches, is there anything we need to do to help make sure that fix goes in? (or is it up to @xedin / @ktoso to nominate it for inclusion?)

TIA,

Joakim

1 Like
3

Thank you for flagging that @hassila.

We nominated and got approved to pick the change to 6.1.1: [6.1.1][SILOptimizer] Prevent devirtualization of call to distributed witness requirements by ktoso · Pull Request #80637 · swiftlang/swift · GitHub

This should get you the fix sooner than waiting for the release/6.1 branch aligned which is aligned with an Xcode release which will be a bit later than this 6.1.1 gets to ship.

Hope this unblocks you! Thanks for reporting issues and keeping an eye on this.

2 Likes
4

Awesome @ktoso, thank's so much for elucidating and getting it in - looking forward!

1 Like
5

May I also nominate On Windows 10, at launch of LLDB, program is unable to access stdout or stdin · Issue #309 · swiftlang/vscode-swift · GitHub here?

Terminal input/output has been broken on Windows for almost three years now (when running/debugging through LLDB) :confused:

The bug is filed in the vscode-swift repo, but the issue seems to be elsewhere.

3 Likes
6

I'd like to nominate the following fixes:

They are small things but help the user experience, if they could be cherry picked for 6.1.1.

7

Thank you everyone who shared nomtion here. However, please follow the nomination process here: Swift.org - Monthly Non-Darwin Swift Releases

1 Like