As a standard pattern, the vendoring script needed some changes, as did
our internal code.
The biggest change here is that BoringSSL has changed its name mangling
scheme. This causes us to no longer need to explicitly write the prefix
out anymore: in fact, doing that causes compiler errors. So this patch
rewrites the code to resolve that issue.
Along the way, I've also added some checks for making sure the name
mangling is correct.
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:
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
* `@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:
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:
The benchmarks have a 2000 alloc wiggle room defined at the per-test
level. It's not obvious why this is there as the numbers seem stable.
Their presence allows for improvements/regressions to go unnoticed which
isn't good.
Modifications:
- Remove the wiggle room
- Rename the benchmark target from NIOSSHBenchmarks to NIOSSLBenchmarks
Result:
Easier to catch regressions/improvements
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.
## Summary
Allocations regressed by 3 around Feb 2, 2025. While that's being
investigated, let's get CI back to green by bumping the threshold
temporarily.
## Test Plan
CI should pass again.
### 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.