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:
* 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.
Update FieldParser.swift availability guard for
```
String(unsafeUninitializedCapacity: unescapedBytes.count)
```
which is only available on Mac Catalyst 14.0 or later
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.
Enable MemberImportVisibility check on all targets. Use a standard
string header and footer to bracket the new block for ease of updating
in the future with scripts.
Co-authored-by: George Barnett <gbarnett@apple.com>
Motivation:
swift-http-structured-headers has been updated to [RFC
9651](https://www.ietf.org/rfc/rfc9651.html).
Modifications:
- Update documentation.
Result:
An up-to-date documentation.
Co-authored-by: Cory Benfield <lukasa@apple.com>
Motivation:
[RFC 9651](https://www.ietf.org/rfc/rfc9651.html) permits serializing an
integer in the range of -999,999,999,999,999 to 999,999,999,999,999
inclusive ([Section
4.1.4-2.1.1](https://www.ietf.org/rfc/rfc9651.html#section-4.1.4-2.1.1)).
As `RFC9651BareItem` takes values `integer` or `date` with an associated
value of type `Int`, that range is implicitly more constrained on 32-bit
platforms to a subset range of `Int32.min` to `Int32.max` inclusive.
Modifications:
- Adjust `RFC9651BareItem` to take values `integer` or `date` with an
associated value of type `Int64` instead, which is sufficient for the
permitted range.
Result:
Compatibility for the Integer and Date Structured Types on 32-bit
platforms.
Motivation:
The parser and serializer for the Display String type have been
implemented. The high-level encoder and decoder should follow.
Modifications:
Implement the encoder and decoder for Display String.
Result:
The StructuredFieldValues module will support the Display String type.
---------
Co-authored-by: Cory Benfield <lukasa@apple.com>
Motivation:
The parser and serializer for the Date type has been implemented. The high-level encoder and decoder should follow.
Modifications:
- Implement the encoder and decoder for Date.
Result:
The StructuredFieldValues module will support the Date type.
Motivation:
RFC 9651 added the Display String Structured Type.
Modifications:
Implement the parser and serializer for Display String in the RawStructuredFieldValues module.
Result:
The RawStructuredFieldValues module will support the Display String type.
Migrate CI to use GitHub Actions.
Motivation:
To migrate to GitHub actions and centralised infrastructure.
Modifications:
Changes of note:
* Adopt swift-format using rules from SwiftNIO
* Remove scripts and docker files which are no longer needed
Result:
Feature parity with old CI.
Motivation:
[RFC 9651](https://www.ietf.org/rfc/rfc9651.html) added the Date Structured Type.
Modifications:
- Implement the parser and serializer for Date in the RawStructuredFieldValues module.
Result:
The RawStructuredFieldValues module will support the Date type.
Motivation:
`swift-http-structured-headers` has to be updated to [RFC 9651](https://www.ietf.org/rfc/rfc9651.html). And it will be convenient for users to have this update as a SemVer minor.
Modifications:
- Deprecate the `BareItem` type and replace it with `RFC9651BareItem`, retaining existing behaviours. Updates for the new RFC will be based on `RFC9651BareItem`.
Result:
The library can be updated to the new RFC in a backward-compatible manner.
Motivation:
We no longer support compilers older than 5.3 (or indeed older than
5.6), so we don't need compiler guards for old ones.
Modifications:
Remove fallback for old compilers.
Result:
Easier to understand code
* Remove Swift 5.5 Dockerfile
Motivation:
Swift 5.5 is no longer supported.
Modifications:
Remove Swift 5.5 Dockerfile
Result:
Swift 5.5 support fully removed
* Remove SHSendable
---------
Co-authored-by: Cory Benfield <lukasa@apple.com>
Motivation:
Policy is to support 3 swift versions and 5.8 has now been released.
Modifications:
Remove Package.swift for 5.5
Result:
Swift 5.5 no longer supported
Motivation:
#fileID introduced in Swift 5.3, so no longer need to use #file anywhere
Modifications:
Changed #file to #filePath or #fileID depending on the situation
Motivation:
We periodically drop support for older Swift versions. Now that
5.7 has been released, 5.4 can be dropped.
Modifications:
- Remove 5.4 specific Package.swift and docker-compose
- Update the 5.7 docker-compose to use the released 5.7 and move from
focal (2004) to jammy (2204)
Results:
Minimum Swift version is 5.5
Motivation
Documentation is nice, and we can help support users by providing useful
clear docs.
Modifications
Add Docc to 5.6 and later builds
Make sure symbol references work
Add overview docs
Result
Nice rendering docs
As outlined in a [Swift forums post in November ’21](https://forums.swift.org/t/swiftnio-swift-version-support/53232), SwiftNIO will only support the latest non-patch Swift release and the 2 immediately prior non-patch versions.
- drop support for Swift 5.2 and 5.3.
- update CI for Swift 5.4 to run on bionic instead of focal to ensure that we still test bionic.
Motivation:
The combination of Ruby and Jazzy are throwing up issues in CI on older
Ubuntu versions.
Modifications:
- Only install Jazzy on focal
- Fix doc generation script to use more recent source-kitten syntax
Results:
- CI doesn't complain
- Docs get built