### Motivation

Now Swift 5.9 is released and 5.10 nightly images are available, we
should update our CI to use the official release for 5.10 and setup a
new CI for 5.10.
 
### Modifications

- Update 5.9 CI to use `swift:5.9-jammy`
- Add new CI for `swiftlang/swift:nightly-5.10-jammy`

### Result

- 5.9 CI is using official released image.
- 5.10 CI can be brought online.

### Test Plan

Running both of these commands locally succeed:

```console
% docker-compose -f docker/docker-compose.yaml -f docker/docker-compose.2204.59.yaml run test
```
```console
% docker-compose -f docker/docker-compose.yaml -f docker/docker-compose.2204.510.yaml run test
```

Bump swift-format to 5.9

### Motivation

As per apple/swift-openapi-generator#175.

### Modifications

Bump swift-format, update to make soundness pass.

### Result

Using swift-format 5.9.

### Test Plan

Soundness passed.


Reviewed by: dnadoba

Builds:
     ✔︎ pull request validation (5.10) - Build finished. 
     ✔︎ pull request validation (5.8) - Build finished. 
     ✔︎ pull request validation (5.9) - Build finished. 
     ✔︎ pull request validation (nightly) - Build finished. 
     ✔︎ pull request validation (soundness) - Build finished. 

#20

Add a soundness --fix flag

### Motivation

When running `./scripts/soundness.sh` produces swift-format warnings, we ask adopters to manually copy/paste a call to swift format to fix the warnings up. This is tedious and unnecessary.

### Modifications

Add a `--fix` option on the `soundness.sh` script to actually apply the fixes as well, avoiding the need to copy/paste long commands.

### Result

Easier fixing up of formatting warnings.

### Test Plan

Manually tested the workflow locally.


Reviewed by: glbrntt

Builds:
     ✔︎ pull request validation (5.10) - Build finished. 
     ✔︎ pull request validation (5.8) - Build finished. 
     ✔︎ pull request validation (5.9) - Build finished. 
     ✔︎ pull request validation (nightly) - Build finished. 
     ✔︎ pull request validation (soundness) - Build finished. 

#22

…tent styling (#23)

### Motivation

- Relates to
[#230](apple/swift-openapi-generator#230)

### Modifications

- Disable respectsExistingLineBreaks .swift-format rule and address
changes requested

### Result

- One of the .swift-format rules will be disabled

### Test Plan

- Run Tests

### Motivation

Surface the Swift version and platform support status from Swift Package
Index.

### Modifications

Added badges, plus a quick link to the docc docs, to the top of the
README.

Also, expanded the supported platforms, we do actually support iOS and
friends (was an oversight not to include it before).

### Result

Easier to quickly see our support matrix, plus the quick link to docs.

### Test Plan

Previewed locally.

### Motivation

On main, the HTTPBody length type changed from Int to Int64.

### Modifications

Adapted the transport with this change.

### Result

Repo builds again when using the latest runtime.

### Test Plan

Adapted tests.

### Motivation

Part of addressing
apple/swift-openapi-generator#75 and
apple/swift-openapi-generator#119.

### Modifications

Bumped Swift tools version to 5.9 and made the `ExistentialAny` build
setting unconditional.

### Result

Building the package requires 5.9 now.

### Test Plan

Ran tests, all passed when using a Swift 5.9 toolchain.

### Motivation

In #26 we bumped the minimum tools version to Swift 5.9, but we left the
`#if swift(>5.9)` compiler directive when enabling existential any by
default.

### Modifications

Remove #if swift(>=5.9) check in Package.swift

### Result

No checking for Swift 5.9+, because that's now the default.

### Test Plan

CI.

Bump to 1.0.0-alpha.1

### Motivation

Prepare for 1.0.0-alpha.1.

### Modifications

- Updated runtime dependency.
- Updated docs.

### Result

Ready to tag 1.0.0-alpha.1.

### Test Plan

All tests pass.


Reviewed by: simonjbeaumont

Builds:
     ✔︎ pull request validation (5.10) - Build finished. 
     ✔︎ pull request validation (5.9) - Build finished. 
     ✔︎ pull request validation (nightly) - Build finished. 
     ✔︎ pull request validation (soundness) - Build finished. 

#28

Handle large payloads on 32bit platforms gracefully

### Motivation

If there's a request payload with a number of bytes that can't fit into 32 bits, we'd crash.

### Modifications

Use a graceful initializer and use `.unknown` (so no `content-length` will be sent) if the size exceeds the max of a 32bit int.

### Result

No crash for large payloads on 32bit platforms.

### Test Plan

Tests pass.


Reviewed by: dnadoba

Builds:
     ✔︎ pull request validation (5.10) - Build finished. 
     ✔︎ pull request validation (5.9) - Build finished. 
     ✔︎ pull request validation (nightly) - Build finished. 
     ✔︎ pull request validation (soundness) - Build finished. 

#29

### Motivation

While this isn't technically necessary, as all versions of a platform
not explicitly mentioned are assumed to be supported, it's better to be
explicit here.

### Modifications

Add `visionOS(.v1)` to the list of supported platforms.

### Result

Clearer support matrix.

### Test Plan

N/A, this is basically just a documentation change.

Default the configuration parameter

### Motivation

The AsyncHTTPClient transport API has undergone changes in recent months and we didn't bring back the default initializer after we adopted the shared EventLoopGroup, allowing you to create a transport with just `let transport = AsyncHTTPClientTransport()`.

### Modifications

Default the configuration parameter in the initializer to be able to do that. It's already documented to work, but it doesn't.

### Result

Match the documented behavior of being able to use `let transport = AsyncHTTPClientTransport()`.

### Test Plan

Tests still pass.


Reviewed by: dnadoba

Builds:
     ✔︎ pull request validation (5.10) - Build finished. 
     ✔︎ pull request validation (5.9) - Build finished. 
     ✔︎ pull request validation (nightly) - Build finished. 
     ✔︎ pull request validation (soundness) - Build finished. 

#32

### Motivation

Recent SwiftPM versions seem to be a bit stricter about using (i.e.,
`import ...`) transitive dependencies without explicitly declaring them
as direct dependencies.

### Modifications

Explicitly depend on the HTTPTypes module from swift-http-types.

### Result

More explicitly declare the dependency graph.

### Test Plan

All tests pass.

### Motivation

We centralize the issues for all the repos in the Swift OpenAPI
Generator project in the generator repo. Using an issue template will
make this even clearer, because it will allow people to use the normal
Github workflow to discover the process and provide a link to where to
file their issue.

### Modifications

Add issue template, redirecting to swift-openapi-generator issues.

### Result

When people try and file an issue, they'll be presented with a button
that takes them to the generator repo issues page.

### Test Plan

Manual.

### Motivation

Prep 1.0 - docs.

### Modifications

See above.

### Result

Updated for 1.0.

### Test Plan

Previewed locally.