The Main CI workflow currently fails on Swift 6.1, 6.2, and 6.3 because
`-Xswiftc -warnings-as-errors` is enabled, while the
`@_implementationOnly` imports in this codebase emit deprecation
warnings (`ImplementationOnlyDeprecated`).
The PR workflow already handles this correctly; this change brings the
main workflow in line.
Specifically:
- 6.1: Drops `-warnings-as-errors` entirely, since this toolchain
doesn't support demoting the ImplementationOnlyDeprecated warning. A
comment explains why.
- 6.2 / 6.3: Adds `-Xswiftc -Wwarning -Xswiftc`
ImplementationOnlyDeprecated to demote the warning while still failing
on other warnings.
Default `TLSConfiguration.curves` is now [`.x25519_MLKEM768`, `.x25519`,
`.secp384r1`], enabling post-quantum hybrid key exchange out of the box.
Users can still set curves to nil to fall back to BoringSSL's built-in
curve list, or override with any custom set.
Updated `quantum-secure-tls.md` to reflect that PQ is enabled by default
and document how to customise or disable it.
Motivation
* The shared `macos_tests.yml` workflow no longer accepts
`xcode_16_2_build_arguments_override` and the `xcode_16_3` input is a
no-op. Passing the removed input causes CI to fail.
* Older Xcodes are being removed from the runners; Swift version inputs
are the replacement.
Modifications
* Replace `xcode_16_2/16_3_build_arguments_override` with
`swift_6_1/6_2/6_3_build_arguments_override` carrying the same
`-Xswiftc -Xfrontend -Xswiftc -require-explicit-sendable` value.
Result
* macOS CI passes again using the Swift version inputs.
Motivation:
Swift 6.0 is no longer supported, we should bump the tools version and
remove it from our CI.
Modifications:
* Bump the Swift tools version to Swift 6.1
* Remove Swift 6.0 jobs where appropriate in main.yml, pull_request.yml
Result:
Code reflects our support window.
---------
Co-authored-by: George Barnett <gbarnett@apple.com>
Motivation:
Swift 6.3 has been released, we should add it to our CI coverage.
Modifications:
Add additional Swift 6.3 jobs where appropriate in main.yml,
pull_request.yml
Result:
Improved test coverage.
Motivation
* Following [GitHub's
announcement](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/),
Node 20 is being deprecated and runners will begin using Node 24 by
default starting March 4th, 2026. Node 20 will reach end-of-life in
April 2026.
Modifications
* Upgrade GitHub Actions to their latest versions to ensure
compatibility with Node 24.
* Replace `actions/checkout@v4` with `actions/checkout@v6` in all
workflow files.
Result
* Workflow files reference `actions/checkout@v6`.
Motivation
* `@main` references to `swiftlang/github-workflows` are deprecated.
Modifications
* Replace `@main` with `@0.0.7` in all workflow files.
* Update benchmark thresholds so CI passes. These seemed to have the
wrong filenames so I'm not sure how it ever worked.
* Add tolerance to benchmarks in line with NIO
Result
* Workflow files reference a pinned version of
`swiftlang/github-workflows`.
Motivation:
* More secure GitHub Actions workflows
Modifications:
Add explicit 'contents: read' permissions to workflows that did not have
explicit permissions defined. This follows GitHub Actions security best
practices by limiting the default GITHUB_TOKEN permissions.
Result:
An extra layer of security.
Motivation:
Unfortunately, `internal import` doesn't do implementation-hiding in the
build system. This means that the C header files do become visible to
all dependencies, which can cause problems when the ssl.h headers from
elsewhere are included.
Modifications:
Revert to `@_implementationOnly` imports.
Result:
Better builds, unfortunately more warnings
Motivation:
Swift 6.2 has been released, we should add it to our CI coverage.
Modifications:
Add additional Swift 6.2 jobs where appropriate in main.yml,
pull_request.yml
Result:
Improved test coverage.
### Motivation:
Some errors do not show up in debug builds. Enabling release mode builds
improves the CI coverage.
### Modifications:
Enable release mode builds for pull requests and scheduled builds on
main.
### Result:
Improved CI coverage.
Motivation:
Swift 5.9 is no longer supported, we should bump the tools version and
remove it from our CI.
Modifications:
* Bump the Swift tools version to Swift 5.10
* Remove Swift 5.9 jobs where appropriate in main.yml, pull_request.yml
Result:
Code reflects our support window.
Motivation:
Swift 6.1 has been released, we should add it to our CI coverage.
Modifications:
Add additional Swift 6.1 jobs where appropriate in main.yml,
pull_request.yml
Result:
Improved test coverage.
### Motivation:
To remove all uses of the older workflow so it can be removed to
simplify the workflows.
### Modifications:
* Switch integration tests to use the newer Swift test matrix workflow,
`swift_test_matrix.yml`
### Result:
This should make no difference to the running of integration tests.
Motivation:
* Improve test coverage
Modifications:
Enable macOS CI to be run on pull request commits and make the use of
the nightly runner pool for main.yml jobs explicit.
Result:
Improved test coverage.
Motivation:
* Improve test coverage
* Check test pass/fail status
* Monitor CI throughput
Modifications:
Enable macOS CI to be run on all merges to main and on a daily timer.
Result:
Improved test coverage run out-of-band at the moment so we can get a
feeling for if any changes need to be made in the repo or in the CI
pipelines to ensure timely and stable checks.
### Motivation:
* `main.yml` and `scheduled.yml` are mostly duplicative.
* Scheduled runs failed because of a deprecated reference to a Swift 5.8
pipeline
### Modifications:
* Unify `main.yml` and `scheduled.yml`
* Remove the reference to the 5.8 pipeline
### Result:
Working scheduled runs.
### Motivation:
This will allow us to decommission the old CI hooks.
### Modifications:
* Migrate the existing tests to use the package-benchmark framework.
* Delete the obsolete integration tests
* Remove allocations test references from the docker files.
### Result:
Allocation counts are checked using GitHub Actions.
Migrate CI to use GitHub Actions.
### Motivation:
To migrate to GitHub actions and centralised infrastructure.
### Modifications:
Changes of note:
* Disable warnings-as-errors until issues with recent NIO changes are
resolved
* Adopt swift-format using rules from SwiftNIO
* Remove scripts which are no longer needed
### Result:
Feature parity with old CI minus allocation tests which remain on the
old CI.