## Motivation:
Swift Crypto 5 is released, but this package only accepts Swift Crypto
versions below 5.0.0, so projects cannot use the two together.
## Modifications:
Widen the accepted Swift Crypto versions to `..<"6.0.0"`, keeping the
existing lower bound.
## Result:
Projects can use Swift Crypto 5 with this package.
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
* `@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 raise the minimum Swift
tools version to 6.0, fix consequent build warnings/errors, and remove
5.10 CI jobs.
Modifications:
- Raised the Swift tools version to 6.0 in both the main
`swift-certificates` package and the Benchmark package.
- Removed the now redundant `StrictConcurrency=complete` flag in
`swift-certificates`' `Package.swift`.
- Removed 5.10 CI job arguments.
- Removed 5.10 benchmark thresholds.
- Added an explicit type annotation to the `package-benchmark` setup
closure to address a build error.
- Updated `VerifierBenchmark` to use newer, non-deprecated
`RFC5280Policy` initializers (as a result of #276).
- Updated a test case in `Tests/X509Tests/PEMTests.swift` to no longer
use a deprecated `String` initializer.
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:
The certificate chain returned by validation has properties that are
currently not expressed in the API. Introducing a type that does so
allows other APIs to build on these properties.
### Modifications:
* Add a new `ValidatedCertificateChain` type and use it as a result type
for certificate validation. Since a validated chain always has at least
a leaf and a root, the type gives direct access to them.
* Deprecate the previous validate function and introduce a replacement.
Update use of the now-deprecated API and duplicate tests to include both
APIs.
### Result:
Certificate validation returns a type that conceptually holds meaning.
Right now, `Certificate` uses the default implementations of `hash` and
`==`, which are member-wise.
We can make this more efficient by only comparing the raw bytes for the
TBS certificate, the signature, and the signature's algorithm.
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:
Now that Swift 5.9 is GM we should update the CI pipelines
Modifications:
* Add a 5.10 nightly docker compose file
* Update the 5.9 compose file to stop using nightlies
* Update benchmark thresholds
Result:
Remove add CI support for 5.10