The Security section links a relative `SECURITY.md`, but no such file
exists in this repository, so the link 404s on the rendered README. This
points it at the repository's [security policy
page](https://github.com/apple/swift-http-structured-headers/security/policy)
instead, which resolves via the org-level default policy (verified 200).
Verified locally on macOS (Swift 6.3.3): `swift build` and `swift test`
both pass.
Prepared with AI assistance (Claude); the missing file and working
replacement URL were both mechanically verified.
Co-authored-by: Zayan Khan <khanzayan200@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
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.
Result
* Workflow files reference a pinned version of
`swiftlang/github-workflows`.
### Motivation:
Swift 5.10 is no longer supported, we should bump the swift-tools
version.
### Modifications:
* Update Swift tools version to 6.0
### Result:
Code reflects our support window.
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.
Update StructuredFieldValueParser to add missing visionOS guard matching
the guards on the called API. This was causing failures to compile for
visionOS
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:
* 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