Skip to content

Require Swift 6.1#278

Draft
glessard wants to merge 1 commit intoapple:mainfrom
glessard:dev/require-swift-6.1
Draft

Require Swift 6.1#278
glessard wants to merge 1 commit intoapple:mainfrom
glessard:dev/require-swift-6.1

Conversation

@glessard
Copy link
Contributor

@glessard glessard commented Jan 7, 2026

Whenever we determine that our next minor version will be cut after the release of Swift 6.3, then we should merge this.

@glessard
Copy link
Contributor Author

glessard commented Jan 7, 2026

@swift-ci please test

- and exclude 6.0 toolchains from executing in CI
@glessard glessard force-pushed the dev/require-swift-6.1 branch from e03b5d7 to 097805e Compare January 7, 2026 01:11
@glessard
Copy link
Contributor Author

glessard commented Jan 7, 2026

@swift-ci please test

@FranzBusch
Copy link
Member

The swiftlang Swift version support strategy is the following:

Packages should support the latest patch releases of the last three minor official Swift releases.

Even though this package isn't part of swiftlang and can follow its own Swift version support strategy it would be good if we could follow it since a lot of the ecosystem is expecting it. This means we should only drop support for 6.0 once 6.4 is released.

@glessard
Copy link
Contributor Author

On the very next line:

For example, if the currently latest Swift release is 6.2.1 then a package would be expected to support 6.2.1, 6.1.3 and 6.0.3.

I read this to mean that once 6.3 is out we can drop 6.0.x; this is what we have done for the other packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants