vapor/vapor (vapor/vapor)
### [`v4.79.0`](https://togithub.com/vapor/vapor/releases/tag/4.79.0): - Add Sendable Conformances to underlying types
[Compare Source](https://togithub.com/vapor/vapor/compare/4.78.2...4.79.0)
#### What's Changed
Add Sendable Conformances to underlying types by [@0xTim](https://togithub.com/0xTim) in [#3054](https://togithub.com/vapor/vapor/issues/3054)
> This adds Sendable annotations to many of Vapor’s types and APIs, including the request handlers.
>
> APIs are marked `@preconcurrency` where it makes sense to reduce warnings for anyone using the release. To fix your code and see the warnings, you can enable strict concurrency checking.
>
> **Note:** this PR does not touch `Request`, `Response` or `Application` as they require fundamental changes that are larger in scope and will be done in a future release.
#### Reviewers
Thanks to the reviewers for their help:
- [@FranzBusch](https://togithub.com/FranzBusch)
- [@Lukasa](https://togithub.com/Lukasa)
###### *This patch was released by [@0xTim](https://togithub.com/0xTim)*
**Full Changelog**: https://github.com/vapor/vapor/compare/4.78.2...4.79.0
### [`v4.78.2`](https://togithub.com/vapor/vapor/releases/tag/4.78.2): - Resolve issue #2650
[Compare Source](https://togithub.com/vapor/vapor/compare/4.78.1...4.78.2)
#### What's Changed
Resolve issue [#2650](https://togithub.com/vapor/vapor/issues/2650) by [@paunik](https://togithub.com/paunik) in [#2674](https://togithub.com/vapor/vapor/issues/2674)
> In order to prevent 5xx internal error we try to:
>
> - validate number of parameters in FormDataDecoder so we can detect when only boundary is present.
#### New Contributor
- [@paunik](https://togithub.com/paunik) made their first contribution in [#2674](https://togithub.com/vapor/vapor/issues/2674) 🎉
###### *This patch was released by [@gwynne](https://togithub.com/gwynne)*
**Full Changelog**: https://github.com/vapor/vapor/compare/4.78.1...4.78.2
### [`v4.78.1`](https://togithub.com/vapor/vapor/releases/tag/4.78.1): - Fix for #2574 Missing quote from value
[Compare Source](https://togithub.com/vapor/vapor/compare/4.78.0...4.78.1)
#### What's Changed
Fix for [#2574](https://togithub.com/vapor/vapor/issues/2574) Missing quote from value by [@paunik](https://togithub.com/paunik) in [#2839](https://togithub.com/vapor/vapor/issues/2839)
> - now quotes are always enforced in `DirectiveSerializer.serialize`
> - adjusted tests
#### New Contributor
- [@paunik](https://togithub.com/paunik) made their first contribution in [#2839](https://togithub.com/vapor/vapor/issues/2839) 🎉
###### *This patch was released by [@gwynne](https://togithub.com/gwynne)*
**Full Changelog**: https://github.com/vapor/vapor/compare/4.78.0...4.78.1
### [`v4.78.0`](https://togithub.com/vapor/vapor/releases/tag/4.78.0): - Allow specifying a timeout for client requests
[Compare Source](https://togithub.com/vapor/vapor/compare/4.77.2...4.78.0)
#### What's Changed
Allow specifying a timeout for client requests by [@ffried](https://togithub.com/ffried) in [#3043](https://togithub.com/vapor/vapor/issues/3043)
> Adds a `timeout` property to `ClientRequest`, which is forwarded to `HTTPClient` by `EventLoopHTTPClient`.
> To use it, the `beforeSend` closure can be used:
>
> ```swift
> request.client.get("http://example.com") {
> $0.timeout = .seconds(5)
> }
> ```
#### New Contributor
- [@ffried](https://togithub.com/ffried) made their first contribution in [#3043](https://togithub.com/vapor/vapor/issues/3043) 🎉
###### *This patch was released by [@gwynne](https://togithub.com/gwynne)*
**Full Changelog**: https://github.com/vapor/vapor/compare/4.77.2...4.78.0
### [`v4.77.2`](https://togithub.com/vapor/vapor/releases/tag/4.77.2): - Update dependencies with known CVEs to the latest versions
[Compare Source](https://togithub.com/vapor/vapor/compare/4.77.1...4.77.2)
###### *This patch was released by [@0xTim](https://togithub.com/0xTim).*
#### What's Changed
Update dependencies with known CVEs to the latest versions by [@0xTim](https://togithub.com/0xTim) in [#3038](https://togithub.com/vapor/vapor/issues/3038)
> Async HTTP Client and SwiftNIO and SwiftNIO extras have CVEs that have been patched. We still depend on versions that are vulnerable, so this updates that.
**Full Changelog**: https://github.com/vapor/vapor/compare/4.77.1...4.77.2
### [`v4.77.1`](https://togithub.com/vapor/vapor/releases/tag/4.77.1): Improve error reporting for `EncodingError` and `DecodingError`
[Compare Source](https://togithub.com/vapor/vapor/compare/4.77.0...4.77.1)
###### *This patch was authored by [@grahamburgsma](https://togithub.com/grahamburgsma) and released by [@0xTim](https://togithub.com/0xTim).*
As `EncodingError` and `DecodingError` both conform to `LocalizedError`, error reporting uses their `localizedDescription` which is just a generic error message.
So this changes the error reporting from:
> The operation could not be completed. The data isn’t in the correct format.
To a description much more useful (for example):
> invalidValue(inf, Swift.EncodingError.Context(codingPath: \[...], debugDescription: "Unable to encode Double.inf directly in JSON.", underlyingError: nil))
### [`v4.77.0`](https://togithub.com/vapor/vapor/releases/tag/4.77.0): Add `ContentContainer.decode(_:as:)`
[Compare Source](https://togithub.com/vapor/vapor/compare/4.76.4...4.77.0)
###### *This patch was authored by [@MahdiBM](https://togithub.com/MahdiBM) and released by [@0xTim](https://togithub.com/0xTim).*
Adds `ContentContainer.decode(_:as:)` to compliment `ContentContainer.encode(_:as:)` to make it easy to override the `Content-Type` if calling an API or decoding a request that returns erroneous headers for the body type.
### [`v4.76.4`](https://togithub.com/vapor/vapor/releases/tag/4.76.4): Fixed drain handler call order in case of asynchronous buffer handling
[Compare Source](https://togithub.com/vapor/vapor/compare/4.76.3...4.76.4)
###### *This patch was authored by [@salpieiev](https://togithub.com/salpieiev) and released by [@0xTim](https://togithub.com/0xTim).*
During request body drain each chunk of data may be handled asynchronously. This may lead to a call of handler with `.end` parameter before previous call with `.buffer(buffer)` finished it's execution.
For example:
1. Open new file descriptor
2. During `.collected` stage write ByteBuffer on disc using this file descriptor
3. During `.end` stage close file descriptor
This fix ensures that file descriptor won't be closed until disc write completes
### [`v4.76.3`](https://togithub.com/vapor/vapor/releases/tag/4.76.3): Don't use UnsafeRawBufferPointer.withMemoryRebound(to:_:) before Swift 5.7.2
[Compare Source](https://togithub.com/vapor/vapor/compare/4.76.2...4.76.3)
###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).*
This API did not exist yet in Swift 5.7.0. It will now only be called in 5.7.2 or later.
(This being said, those still using Xcode 14.0.x - the only known affected version - should upgrade to 14.2 (if still running Monterey) or 14.3 (if running Ventura).)
### [`v4.76.2`](https://togithub.com/vapor/vapor/releases/tag/4.76.2): Fix `Range: bytes=0-0` header not working properly
[Compare Source](https://togithub.com/vapor/vapor/compare/4.76.1...4.76.2)
###### *This patch was authored by [@ptoffy](https://togithub.com/ptoffy) and released by [@0xTim](https://togithub.com/0xTim).*
This aims to fix the bug found in https://discord.com/channels/431917998102675485/519613337638797315/1104341522473812039, which returned a `Bad Response` rather then returning the first byte of the requested content when the `Range: bytes=0-0` request header was used
### [`v4.76.1`](https://togithub.com/vapor/vapor/releases/tag/4.76.1): Improved error logging
[Compare Source](https://togithub.com/vapor/vapor/compare/4.76.0...4.76.1)
###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).*
Some kinds of errors provide additional "debug" information, which can give much more detail than the "plain" description of the error. In many cases this debug info can contain sensitive data, such as specifics about a database schema, so Vapor only uses the plain description when sending errors to clients (and in release environments, *all* details are suppressed).
To date, the plain description has also been used for logging errors. This can make it very difficult for developers to figure out what's going wrong with their code if the error in question only provides meaningful information in its debug data - for example, the PostgreSQL database driver implementation does this rather than relying on a higher-level layer like Vapor to obfuscate potentially sensitive information. This PR changes the logging of errors to include the debug information (and *only* the logging; the responses sent to clients are unchanged).
### [`v4.76.0`](https://togithub.com/vapor/vapor/releases/tag/4.76.0): Update Minimum Swift Version to 5.6
[Compare Source](https://togithub.com/vapor/vapor/compare/4.75.2...4.76.0)
###### *This patch was authored and released by [@0xTim](https://togithub.com/0xTim).*
Inline with the Swift version support and NIO's supported version, this sets the minimum supported Swift version to 5.6 now that Swift 5.8 is released.
This is also the first step in adopting `Sendable` properly across Vapor
### [`v4.75.2`](https://togithub.com/vapor/vapor/compare/4.75.1...4.75.2)
[Compare Source](https://togithub.com/vapor/vapor/compare/4.75.1...4.75.2)
### [`v4.75.1`](https://togithub.com/vapor/vapor/releases/tag/4.75.1): Fix crash when collecting the body
[Compare Source](https://togithub.com/vapor/vapor/compare/4.75.0...4.75.1)
###### *This patch was authored and released by [@0xTim](https://togithub.com/0xTim).*
Fixes an issue where users may experience a crash when collecting the body in async routes due to pre-concurrency assumptions made by Vapor.
Resolves [#2990](https://togithub.com/vapor/vapor/issues/2990)
### [`v4.75.0`](https://togithub.com/vapor/vapor/releases/tag/4.75.0): Fix multiple correctness issues
[Compare Source](https://togithub.com/vapor/vapor/compare/4.74.2...4.75.0)
###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).*
Here's a list of changes:
- `StackTrace` no longer severely misuses pointers or invokes undefined behavior when gathering backtraces on Linux. It also no longer has a number of implicit fatal error code paths.
- Several deprecation warnings that show up when building with 5.8+ are gone.
- Concurrency support now correctly back-deploys as far as macOS 10.15. As a side effect, the minimum Swift version has increased from 5.5 to 5.5.2.
- The `Deployment` example target has been significantly improved and no longer references local paths on [@tanner0101](https://togithub.com/tanner0101)'s computer 😆
- The TOTP/HOTP logic is now both faster and safer (no more use of unsafe pointers, in particular).
- `DecoderWrapper`, an unsafe `Codable` hack with serious pitfalls, has been hard-deprecated.
- `PlaintextEncoder` and `PlaintextDecoder` have been significantly cleaned up and improved. All `fatalError()`s have been removed, performance has been noticeably improved, and errors are more accurate.
- `URLEncodedFormEncoder` and `URLEncodedFormDecoder` got the same treatment.
- The entire `Validation` submodule has been overhauled to fix systemic misuses of `Codable` that were starting to cause noticeable problems.
- As a side effect of said overhaul, `ValidationKey` is now deprecated in favor of using the essentially identical `BasicCodingKey` type.
- `ContentContainer` and `URLQueryContainer` received the same "fix `Codable` usage" treatment.
- `ContentConfiguration` now throws more useful errors.
- When `CodingKeyRepresentable` is available in the stdlib (Swift 5.6+), Vapor's protocol of the same name now becomes a `typealias` for it.
### [`v4.74.2`](https://togithub.com/vapor/vapor/releases/tag/4.74.2): Imports fixes
[Compare Source](https://togithub.com/vapor/vapor/compare/4.74.1...4.74.2)
###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).*
### [`v4.74.1`](https://togithub.com/vapor/vapor/releases/tag/4.74.1): Correctly handle invalid numbers in range validations
[Compare Source](https://togithub.com/vapor/vapor/compare/4.74.0...4.74.1)
###### *This patch was authored by [@fred-sch](https://togithub.com/fred-sch) and released by [@0xTim](https://togithub.com/0xTim).*
Previously trying to perform a range validation check on `Float.nan` would cause a `fatalError` - this correctly handles it and throws an error instead.
Closes [https://github.com/vapor/vapor/issues/2965](https://togithub.com/vapor/vapor/issues/2965).
### [`v4.74.0`](https://togithub.com/vapor/vapor/releases/tag/4.74.0): Revert "Add support for asynchronous body stream writing"
[Compare Source](https://togithub.com/vapor/vapor/compare/4.73.0...4.74.0)
###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).*
We're reverting [#2939](https://togithub.com/vapor/vapor/issues/2939), which was accidentally merged early, as a precautionary measure. A new PR will be opened to track this work.
### [`v4.73.0`](https://togithub.com/vapor/vapor/releases/tag/4.73.0): Add support for asynchronous body stream writing
[Compare Source](https://togithub.com/vapor/vapor/compare/4.72.1...4.73.0)
###### *This patch was authored and released by [@Joannis](https://togithub.com/Joannis).*
- Fixes [#2930](https://togithub.com/vapor/vapor/issues/2930) - a crash when users try to write a body from within a task towards the ELF APIs.
- Introduces a new API for writing chunked HTTP response bodies
- Adds a helper that automatically managed failing and closing streams
### [`v4.72.1`](https://togithub.com/vapor/vapor/releases/tag/4.72.1): Add support for Cache-Control header 'immutable' attribute
[Compare Source](https://togithub.com/vapor/vapor/compare/4.72.0...4.72.1)
###### *This patch was authored by [@Palleas](https://togithub.com/Palleas) and released by [@0xTim](https://togithub.com/0xTim).*
Improve parsing of Cache-Control header to parse the `immutable` attribute.
### [`v4.72.0`](https://togithub.com/vapor/vapor/releases/tag/4.72.0): Add 308 Redirect
[Compare Source](https://togithub.com/vapor/vapor/compare/4.71.1...4.72.0)
###### *This patch was authored by [@NeedleInAJayStack](https://togithub.com/NeedleInAJayStack) and released by [@0xTim](https://togithub.com/0xTim).*
Adds support for a `308 redirect` to support POST method redirection. This is important because not all user-agents preserve the method and body through a 301 redirect: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/301
`redirect(to:type:)` is now deprecated in favour of `redirect(to:redirectType:)`
### [`v4.71.1`](https://togithub.com/vapor/vapor/releases/tag/4.71.1): Better `DecodingError` description
[Compare Source](https://togithub.com/vapor/vapor/compare/4.71.0...4.71.1)
###### *This patch was authored by [@MahdiBM](https://togithub.com/MahdiBM) and released by [@0xTim](https://togithub.com/0xTim).*
The `DecodingError`'s description, when returned from HTTP requests, was missing some important info and sometimes was not clear enough. Hopefully this PR can resolve that issue.
### [`v4.71.0`](https://togithub.com/vapor/vapor/releases/tag/4.71.0): FileMiddleware redirect option
[Compare Source](https://togithub.com/vapor/vapor/compare/4.70.0...4.71.0)
###### *This patch was authored by [@NeedleInAJayStack](https://togithub.com/NeedleInAJayStack) and released by [@0xTim](https://togithub.com/0xTim).*
Previously, FileMiddleware would just serve the default file when requesting a directory with no trailing slash. This caused rendering issues when the default file loaded additional resources by relative path. This adds an option to either redirect to the url with a trailing slash (fixing rendering issues), or just pass the request through the middleware. The default is set to a redirect to preserve the intended functionality of FileMiddleware
### [`v4.70.0`](https://togithub.com/vapor/vapor/releases/tag/4.70.0): Expose Vapor Request's request-id value, so that it can be passed into logging from other libraries
[Compare Source](https://togithub.com/vapor/vapor/compare/4.69.2...4.70.0)
###### *This patch was authored by [@Joannis](https://togithub.com/Joannis) and released by [@0xTim](https://togithub.com/0xTim).*
Exposes the Request's ID as a new property on `Request` as `requestID`. This is useful for any libraries or users who want to be able to trace the request ID through a request handler.
### [`v4.69.2`](https://togithub.com/vapor/vapor/releases/tag/4.69.2): Fix: FileIO headers
[Compare Source](https://togithub.com/vapor/vapor/compare/4.69.1...4.69.2)
###### *This patch was authored by [@NeedleInAJayStack](https://togithub.com/NeedleInAJayStack) and released by [@Joannis](https://togithub.com/Joannis).*
- Adds `Last-Modified` header to file requests
- Fixes `ETag` header formatting in file requests: According to [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag), the `ETag` header should start and end with double-quotes.
### [`v4.69.1`](https://togithub.com/vapor/vapor/releases/tag/4.69.1): Allow URLEncodedForms to decode 'on' value als Bool => true
[Compare Source](https://togithub.com/vapor/vapor/compare/4.69.0...4.69.1)
###### *This patch was authored by [@bobvoorneveld](https://togithub.com/bobvoorneveld) and released by [@Joannis](https://togithub.com/Joannis).*
When a HTML form uses a checkbox to check something as a Bool, it sends the 'on' value if checked.
The URLEncodedForms decoder should be able to handle that.
struct FormData: Decodable {
let isActive: Bool
}
let formData = try req.content.decode(FormData.self)
fixes [#2444](https://togithub.com/vapor/vapor/issues/2444)
### [`v4.69.0`](https://togithub.com/vapor/vapor/releases/tag/4.69.0): FileMiddleware: Add convenience support for serving files from a Bundle
[Compare Source](https://togithub.com/vapor/vapor/compare/4.68.0...4.69.0)
###### *This patch was authored by [@MrSkwiggs](https://togithub.com/MrSkwiggs) and released by [@Joannis](https://togithub.com/Joannis).*
Adds support for instantiating a `FileMiddleware` to serve files from a Bundle. This comes in handy when Vapor is used as a dependency in an `Xcodeproj` and simply passing the `publicDirectory` path is not sufficient.
### [`v4.68.0`](https://togithub.com/vapor/vapor/releases/tag/4.68.0): Enable back deployment of Concurrency
[Compare Source](https://togithub.com/vapor/vapor/compare/4.67.5...4.68.0)
###### *This patch was authored by [@sevki](https://togithub.com/sevki) and released by [@0xTim](https://togithub.com/0xTim).*
Enable back deployment of Vapor's concurrency APIs on older Apple platforms.
This also drops support for Swift versions < 5.5.2 to match SwiftNIO
### [`v4.67.5`](https://togithub.com/vapor/vapor/releases/tag/4.67.5): Prevent vapor streaming requests from randomly losing a first chunk, stalling the request
[Compare Source](https://togithub.com/vapor/vapor/compare/4.67.4...4.67.5)
###### *This patch was authored by [@Joannis](https://togithub.com/Joannis) and released by [@0xTim](https://togithub.com/0xTim).*
Fixes a bug where a streaming body from a request was not processing a chunk, causing the request to stall. This happened when a handler was being set at the exact moment a chunk was being processed, causing the chunk to be added to a now irrelevant array that was just processed while switching to a streaming callback.
See [#2906](https://togithub.com/vapor/vapor/issues/2906)
### [`v4.67.4`](https://togithub.com/vapor/vapor/releases/tag/4.67.4): Fix encoding/decoding an array of dates with URL Encoding
[Compare Source](https://togithub.com/vapor/vapor/compare/4.67.3...4.67.4)
###### *This patch was authored and released by [@Joannis](https://togithub.com/Joannis).*
Fixes a bug where an Array of Dates wouldn't be encoded or decoded when using URL encoding.
### [`v4.67.3`](https://togithub.com/vapor/vapor/releases/tag/4.67.3): Fix Stream Callback never being called in close
[Compare Source](https://togithub.com/vapor/vapor/compare/4.67.2...4.67.3)
###### *This patch was authored and released by [@0xTim](https://togithub.com/0xTim).*
Fixes a bug where abandoned requests mean that the stream callback is never invoked. This happens when a client sends a request, the server starts processing it but hasn't constructed the `Response` and then the client closes early. The response is discarded, as is the stream callback so it never gets invoked. This fixes that issue
### [`v4.67.2`](https://togithub.com/vapor/vapor/releases/tag/4.67.2): Fix unused generator parameter in Array.random(count:using:)
[Compare Source](https://togithub.com/vapor/vapor/compare/4.67.1...4.67.2)
###### *This patch was authored by [@michal-tomlein](https://togithub.com/michal-tomlein) and released by [@0xTim](https://togithub.com/0xTim).*
The `generator` parameter in `Array.random(count:using:)` was unused in what appears to be a copy-paste error. This change passes it down to `FixedWidthInteger.random(using:)`, which was the original intention.
### [`v4.67.1`](https://togithub.com/vapor/vapor/releases/tag/4.67.1): Fix 24h timeformat for `expire` and `last-modified` header
[Compare Source](https://togithub.com/vapor/vapor/compare/4.67.0...4.67.1)
###### *This patch was authored by [@patrick-zippenfenig](https://togithub.com/patrick-zippenfenig) and released by [@0xTim](https://togithub.com/0xTim).*
`Expire` and `Last-Modified` header were encoding the hour part in 12h format (`hh`) instead of 24h format (`HH`). This results in timestamps being 12 hours off for all afternoon hours. This fixes the format used to follow the [spec](https://httpwg.org/specs/rfc9110.html#field.last-modified) correctly and adds tests to ensure no regressions.
### [`v4.67.0`](https://togithub.com/vapor/vapor/releases/tag/4.67.0): Conforms `Request.Body` to `AsyncSequence`
[Compare Source](https://togithub.com/vapor/vapor/compare/4.66.1...4.67.0)
###### *This patch was authored by [@mcritz](https://togithub.com/mcritz) and released by [@0xTim](https://togithub.com/0xTim).*
This PR wraps `Request.Body.drain()` as a modern Swift `AsyncSequence`.
This is useful to *stream* bytes from request rather than collecting them in memory. Example: A route could handle a multigigbyte file upload like this:
```swift
do {
let nioFileHandle = try NIOFileHandle(path: filePath, mode: .write)
var offset: Int64 = 0
for try await bytes in req.body {
try await req.application.fileio.write(fileHandle: nioFileHandle,
toOffset: offset,
buffer: bytes,
eventLoop: req.eventLoop).get()
offset += Int64(bytes.readableBytes)
try nioFileHandle.close()
}
} catch {
...
}
```
### [`v4.66.1`](https://togithub.com/vapor/vapor/releases/tag/4.66.1): Migrate from `Lock` to `NIOLock`
[Compare Source](https://togithub.com/vapor/vapor/compare/4.66.0...4.66.1)
###### *This patch was authored by [@MahdiBM](https://togithub.com/MahdiBM) and released by [@0xTim](https://togithub.com/0xTim).*
`Lock` has recently been deprecated in favor of `NIOLock`.
##### Changes
All `Lock`s have been renamed to `NIOLock`.
### [`v4.66.0`](https://togithub.com/vapor/vapor/releases/tag/4.66.0): Prevent vapor from crashing during a crash in third-party code, obfuscating the real problem
[Compare Source](https://togithub.com/vapor/vapor/compare/4.65.2...4.66.0)
###### *This patch was authored by [@Joannis](https://togithub.com/Joannis) and released by [@0xTim](https://togithub.com/0xTim).*
If a third-party library or user defined code crashed a Vapor app, the Vapor Application deinit will crash the app before the real issue pops up. This leads to frustrating debug sessions
### [`v4.65.2`](https://togithub.com/vapor/vapor/releases/tag/4.65.2): Fixing issue #2755: updating config storage inside HTTPServer
[Compare Source](https://togithub.com/vapor/vapor/compare/4.65.1...4.65.2)
###### *This patch was authored by [@rkreutz](https://togithub.com/rkreutz) and released by [@gwynne](https://togithub.com/gwynne).*
We can update application.storage from within HTTPServer, this way we can keep any changes that happen to the configuration internally up-to-date with the application storage.
This possibly has the least changes and less surface of potential flaws, since we are only adding an extra param and working on top of it. However, now we are setting the application storage from within `HTTPServer`, there is no issue with that, is just that now we have 2 places changing the storage for the config.
Resolves [#2755](https://togithub.com/vapor/vapor/issues/2755)
### [`v4.65.1`](https://togithub.com/vapor/vapor/releases/tag/4.65.1): Add missing protocol `ExpressibleByStringLiteral` to `HTTPHeaders.Name`
[Compare Source](https://togithub.com/vapor/vapor/compare/4.65.0...4.65.1)
###### *This patch was authored by [@grahamburgsma](https://togithub.com/grahamburgsma) and released by [@0xTim](https://togithub.com/0xTim).*
Add missing protocol `ExpressibleByStringLiteral` to `HTTPHeaders.Name`. The implementation `init(stringLiteral:)` was there, but the actual protocol was missing.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
from: "4.65.0"->from: "4.79.0"Release Notes
vapor/vapor (vapor/vapor)
### [`v4.79.0`](https://togithub.com/vapor/vapor/releases/tag/4.79.0): - Add Sendable Conformances to underlying types [Compare Source](https://togithub.com/vapor/vapor/compare/4.78.2...4.79.0) #### What's Changed Add Sendable Conformances to underlying types by [@0xTim](https://togithub.com/0xTim) in [#3054](https://togithub.com/vapor/vapor/issues/3054) > This adds Sendable annotations to many of Vapor’s types and APIs, including the request handlers. > > APIs are marked `@preconcurrency` where it makes sense to reduce warnings for anyone using the release. To fix your code and see the warnings, you can enable strict concurrency checking. > > **Note:** this PR does not touch `Request`, `Response` or `Application` as they require fundamental changes that are larger in scope and will be done in a future release. #### Reviewers Thanks to the reviewers for their help: - [@FranzBusch](https://togithub.com/FranzBusch) - [@Lukasa](https://togithub.com/Lukasa) ###### *This patch was released by [@0xTim](https://togithub.com/0xTim)* **Full Changelog**: https://github.com/vapor/vapor/compare/4.78.2...4.79.0 ### [`v4.78.2`](https://togithub.com/vapor/vapor/releases/tag/4.78.2): - Resolve issue #2650 [Compare Source](https://togithub.com/vapor/vapor/compare/4.78.1...4.78.2) #### What's Changed Resolve issue [#2650](https://togithub.com/vapor/vapor/issues/2650) by [@paunik](https://togithub.com/paunik) in [#2674](https://togithub.com/vapor/vapor/issues/2674) > In order to prevent 5xx internal error we try to: > > - validate number of parameters in FormDataDecoder so we can detect when only boundary is present. #### New Contributor - [@paunik](https://togithub.com/paunik) made their first contribution in [#2674](https://togithub.com/vapor/vapor/issues/2674) 🎉 ###### *This patch was released by [@gwynne](https://togithub.com/gwynne)* **Full Changelog**: https://github.com/vapor/vapor/compare/4.78.1...4.78.2 ### [`v4.78.1`](https://togithub.com/vapor/vapor/releases/tag/4.78.1): - Fix for #2574 Missing quote from value [Compare Source](https://togithub.com/vapor/vapor/compare/4.78.0...4.78.1) #### What's Changed Fix for [#2574](https://togithub.com/vapor/vapor/issues/2574) Missing quote from value by [@paunik](https://togithub.com/paunik) in [#2839](https://togithub.com/vapor/vapor/issues/2839) > - now quotes are always enforced in `DirectiveSerializer.serialize` > - adjusted tests #### New Contributor - [@paunik](https://togithub.com/paunik) made their first contribution in [#2839](https://togithub.com/vapor/vapor/issues/2839) 🎉 ###### *This patch was released by [@gwynne](https://togithub.com/gwynne)* **Full Changelog**: https://github.com/vapor/vapor/compare/4.78.0...4.78.1 ### [`v4.78.0`](https://togithub.com/vapor/vapor/releases/tag/4.78.0): - Allow specifying a timeout for client requests [Compare Source](https://togithub.com/vapor/vapor/compare/4.77.2...4.78.0) #### What's Changed Allow specifying a timeout for client requests by [@ffried](https://togithub.com/ffried) in [#3043](https://togithub.com/vapor/vapor/issues/3043) > Adds a `timeout` property to `ClientRequest`, which is forwarded to `HTTPClient` by `EventLoopHTTPClient`. > To use it, the `beforeSend` closure can be used: > > ```swift > request.client.get("http://example.com") { > $0.timeout = .seconds(5) > } > ``` #### New Contributor - [@ffried](https://togithub.com/ffried) made their first contribution in [#3043](https://togithub.com/vapor/vapor/issues/3043) 🎉 ###### *This patch was released by [@gwynne](https://togithub.com/gwynne)* **Full Changelog**: https://github.com/vapor/vapor/compare/4.77.2...4.78.0 ### [`v4.77.2`](https://togithub.com/vapor/vapor/releases/tag/4.77.2): - Update dependencies with known CVEs to the latest versions [Compare Source](https://togithub.com/vapor/vapor/compare/4.77.1...4.77.2) ###### *This patch was released by [@0xTim](https://togithub.com/0xTim).* #### What's Changed Update dependencies with known CVEs to the latest versions by [@0xTim](https://togithub.com/0xTim) in [#3038](https://togithub.com/vapor/vapor/issues/3038) > Async HTTP Client and SwiftNIO and SwiftNIO extras have CVEs that have been patched. We still depend on versions that are vulnerable, so this updates that. **Full Changelog**: https://github.com/vapor/vapor/compare/4.77.1...4.77.2 ### [`v4.77.1`](https://togithub.com/vapor/vapor/releases/tag/4.77.1): Improve error reporting for `EncodingError` and `DecodingError` [Compare Source](https://togithub.com/vapor/vapor/compare/4.77.0...4.77.1) ###### *This patch was authored by [@grahamburgsma](https://togithub.com/grahamburgsma) and released by [@0xTim](https://togithub.com/0xTim).* As `EncodingError` and `DecodingError` both conform to `LocalizedError`, error reporting uses their `localizedDescription` which is just a generic error message. So this changes the error reporting from: > The operation could not be completed. The data isn’t in the correct format. To a description much more useful (for example): > invalidValue(inf, Swift.EncodingError.Context(codingPath: \[...], debugDescription: "Unable to encode Double.inf directly in JSON.", underlyingError: nil)) ### [`v4.77.0`](https://togithub.com/vapor/vapor/releases/tag/4.77.0): Add `ContentContainer.decode(_:as:)` [Compare Source](https://togithub.com/vapor/vapor/compare/4.76.4...4.77.0) ###### *This patch was authored by [@MahdiBM](https://togithub.com/MahdiBM) and released by [@0xTim](https://togithub.com/0xTim).* Adds `ContentContainer.decode(_:as:)` to compliment `ContentContainer.encode(_:as:)` to make it easy to override the `Content-Type` if calling an API or decoding a request that returns erroneous headers for the body type. ### [`v4.76.4`](https://togithub.com/vapor/vapor/releases/tag/4.76.4): Fixed drain handler call order in case of asynchronous buffer handling [Compare Source](https://togithub.com/vapor/vapor/compare/4.76.3...4.76.4) ###### *This patch was authored by [@salpieiev](https://togithub.com/salpieiev) and released by [@0xTim](https://togithub.com/0xTim).* During request body drain each chunk of data may be handled asynchronously. This may lead to a call of handler with `.end` parameter before previous call with `.buffer(buffer)` finished it's execution. For example: 1. Open new file descriptor 2. During `.collected` stage write ByteBuffer on disc using this file descriptor 3. During `.end` stage close file descriptor This fix ensures that file descriptor won't be closed until disc write completes ### [`v4.76.3`](https://togithub.com/vapor/vapor/releases/tag/4.76.3): Don't use UnsafeRawBufferPointer.withMemoryRebound(to:_:) before Swift 5.7.2 [Compare Source](https://togithub.com/vapor/vapor/compare/4.76.2...4.76.3) ###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).* This API did not exist yet in Swift 5.7.0. It will now only be called in 5.7.2 or later. (This being said, those still using Xcode 14.0.x - the only known affected version - should upgrade to 14.2 (if still running Monterey) or 14.3 (if running Ventura).) ### [`v4.76.2`](https://togithub.com/vapor/vapor/releases/tag/4.76.2): Fix `Range: bytes=0-0` header not working properly [Compare Source](https://togithub.com/vapor/vapor/compare/4.76.1...4.76.2) ###### *This patch was authored by [@ptoffy](https://togithub.com/ptoffy) and released by [@0xTim](https://togithub.com/0xTim).* This aims to fix the bug found in https://discord.com/channels/431917998102675485/519613337638797315/1104341522473812039, which returned a `Bad Response` rather then returning the first byte of the requested content when the `Range: bytes=0-0` request header was used ### [`v4.76.1`](https://togithub.com/vapor/vapor/releases/tag/4.76.1): Improved error logging [Compare Source](https://togithub.com/vapor/vapor/compare/4.76.0...4.76.1) ###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).* Some kinds of errors provide additional "debug" information, which can give much more detail than the "plain" description of the error. In many cases this debug info can contain sensitive data, such as specifics about a database schema, so Vapor only uses the plain description when sending errors to clients (and in release environments, *all* details are suppressed). To date, the plain description has also been used for logging errors. This can make it very difficult for developers to figure out what's going wrong with their code if the error in question only provides meaningful information in its debug data - for example, the PostgreSQL database driver implementation does this rather than relying on a higher-level layer like Vapor to obfuscate potentially sensitive information. This PR changes the logging of errors to include the debug information (and *only* the logging; the responses sent to clients are unchanged). ### [`v4.76.0`](https://togithub.com/vapor/vapor/releases/tag/4.76.0): Update Minimum Swift Version to 5.6 [Compare Source](https://togithub.com/vapor/vapor/compare/4.75.2...4.76.0) ###### *This patch was authored and released by [@0xTim](https://togithub.com/0xTim).* Inline with the Swift version support and NIO's supported version, this sets the minimum supported Swift version to 5.6 now that Swift 5.8 is released. This is also the first step in adopting `Sendable` properly across Vapor ### [`v4.75.2`](https://togithub.com/vapor/vapor/compare/4.75.1...4.75.2) [Compare Source](https://togithub.com/vapor/vapor/compare/4.75.1...4.75.2) ### [`v4.75.1`](https://togithub.com/vapor/vapor/releases/tag/4.75.1): Fix crash when collecting the body [Compare Source](https://togithub.com/vapor/vapor/compare/4.75.0...4.75.1) ###### *This patch was authored and released by [@0xTim](https://togithub.com/0xTim).* Fixes an issue where users may experience a crash when collecting the body in async routes due to pre-concurrency assumptions made by Vapor. Resolves [#2990](https://togithub.com/vapor/vapor/issues/2990) ### [`v4.75.0`](https://togithub.com/vapor/vapor/releases/tag/4.75.0): Fix multiple correctness issues [Compare Source](https://togithub.com/vapor/vapor/compare/4.74.2...4.75.0) ###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).* Here's a list of changes: - `StackTrace` no longer severely misuses pointers or invokes undefined behavior when gathering backtraces on Linux. It also no longer has a number of implicit fatal error code paths. - Several deprecation warnings that show up when building with 5.8+ are gone. - Concurrency support now correctly back-deploys as far as macOS 10.15. As a side effect, the minimum Swift version has increased from 5.5 to 5.5.2. - The `Deployment` example target has been significantly improved and no longer references local paths on [@tanner0101](https://togithub.com/tanner0101)'s computer 😆 - The TOTP/HOTP logic is now both faster and safer (no more use of unsafe pointers, in particular). - `DecoderWrapper`, an unsafe `Codable` hack with serious pitfalls, has been hard-deprecated. - `PlaintextEncoder` and `PlaintextDecoder` have been significantly cleaned up and improved. All `fatalError()`s have been removed, performance has been noticeably improved, and errors are more accurate. - `URLEncodedFormEncoder` and `URLEncodedFormDecoder` got the same treatment. - The entire `Validation` submodule has been overhauled to fix systemic misuses of `Codable` that were starting to cause noticeable problems. - As a side effect of said overhaul, `ValidationKey` is now deprecated in favor of using the essentially identical `BasicCodingKey` type. - `ContentContainer` and `URLQueryContainer` received the same "fix `Codable` usage" treatment. - `ContentConfiguration` now throws more useful errors. - When `CodingKeyRepresentable` is available in the stdlib (Swift 5.6+), Vapor's protocol of the same name now becomes a `typealias` for it. ### [`v4.74.2`](https://togithub.com/vapor/vapor/releases/tag/4.74.2): Imports fixes [Compare Source](https://togithub.com/vapor/vapor/compare/4.74.1...4.74.2) ###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).* ### [`v4.74.1`](https://togithub.com/vapor/vapor/releases/tag/4.74.1): Correctly handle invalid numbers in range validations [Compare Source](https://togithub.com/vapor/vapor/compare/4.74.0...4.74.1) ###### *This patch was authored by [@fred-sch](https://togithub.com/fred-sch) and released by [@0xTim](https://togithub.com/0xTim).* Previously trying to perform a range validation check on `Float.nan` would cause a `fatalError` - this correctly handles it and throws an error instead. Closes [https://github.com/vapor/vapor/issues/2965](https://togithub.com/vapor/vapor/issues/2965). ### [`v4.74.0`](https://togithub.com/vapor/vapor/releases/tag/4.74.0): Revert "Add support for asynchronous body stream writing" [Compare Source](https://togithub.com/vapor/vapor/compare/4.73.0...4.74.0) ###### *This patch was authored and released by [@gwynne](https://togithub.com/gwynne).* We're reverting [#2939](https://togithub.com/vapor/vapor/issues/2939), which was accidentally merged early, as a precautionary measure. A new PR will be opened to track this work. ### [`v4.73.0`](https://togithub.com/vapor/vapor/releases/tag/4.73.0): Add support for asynchronous body stream writing [Compare Source](https://togithub.com/vapor/vapor/compare/4.72.1...4.73.0) ###### *This patch was authored and released by [@Joannis](https://togithub.com/Joannis).* - Fixes [#2930](https://togithub.com/vapor/vapor/issues/2930) - a crash when users try to write a body from within a task towards the ELF APIs. - Introduces a new API for writing chunked HTTP response bodies - Adds a helper that automatically managed failing and closing streams ### [`v4.72.1`](https://togithub.com/vapor/vapor/releases/tag/4.72.1): Add support for Cache-Control header 'immutable' attribute [Compare Source](https://togithub.com/vapor/vapor/compare/4.72.0...4.72.1) ###### *This patch was authored by [@Palleas](https://togithub.com/Palleas) and released by [@0xTim](https://togithub.com/0xTim).* Improve parsing of Cache-Control header to parse the `immutable` attribute. ### [`v4.72.0`](https://togithub.com/vapor/vapor/releases/tag/4.72.0): Add 308 Redirect [Compare Source](https://togithub.com/vapor/vapor/compare/4.71.1...4.72.0) ###### *This patch was authored by [@NeedleInAJayStack](https://togithub.com/NeedleInAJayStack) and released by [@0xTim](https://togithub.com/0xTim).* Adds support for a `308 redirect` to support POST method redirection. This is important because not all user-agents preserve the method and body through a 301 redirect: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/301 `redirect(to:type:)` is now deprecated in favour of `redirect(to:redirectType:)` ### [`v4.71.1`](https://togithub.com/vapor/vapor/releases/tag/4.71.1): Better `DecodingError` description [Compare Source](https://togithub.com/vapor/vapor/compare/4.71.0...4.71.1) ###### *This patch was authored by [@MahdiBM](https://togithub.com/MahdiBM) and released by [@0xTim](https://togithub.com/0xTim).* The `DecodingError`'s description, when returned from HTTP requests, was missing some important info and sometimes was not clear enough. Hopefully this PR can resolve that issue. ### [`v4.71.0`](https://togithub.com/vapor/vapor/releases/tag/4.71.0): FileMiddleware redirect option [Compare Source](https://togithub.com/vapor/vapor/compare/4.70.0...4.71.0) ###### *This patch was authored by [@NeedleInAJayStack](https://togithub.com/NeedleInAJayStack) and released by [@0xTim](https://togithub.com/0xTim).* Previously, FileMiddleware would just serve the default file when requesting a directory with no trailing slash. This caused rendering issues when the default file loaded additional resources by relative path. This adds an option to either redirect to the url with a trailing slash (fixing rendering issues), or just pass the request through the middleware. The default is set to a redirect to preserve the intended functionality of FileMiddleware ### [`v4.70.0`](https://togithub.com/vapor/vapor/releases/tag/4.70.0): Expose Vapor Request's request-id value, so that it can be passed into logging from other libraries [Compare Source](https://togithub.com/vapor/vapor/compare/4.69.2...4.70.0) ###### *This patch was authored by [@Joannis](https://togithub.com/Joannis) and released by [@0xTim](https://togithub.com/0xTim).* Exposes the Request's ID as a new property on `Request` as `requestID`. This is useful for any libraries or users who want to be able to trace the request ID through a request handler. ### [`v4.69.2`](https://togithub.com/vapor/vapor/releases/tag/4.69.2): Fix: FileIO headers [Compare Source](https://togithub.com/vapor/vapor/compare/4.69.1...4.69.2) ###### *This patch was authored by [@NeedleInAJayStack](https://togithub.com/NeedleInAJayStack) and released by [@Joannis](https://togithub.com/Joannis).* - Adds `Last-Modified` header to file requests - Fixes `ETag` header formatting in file requests: According to [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag), the `ETag` header should start and end with double-quotes. ### [`v4.69.1`](https://togithub.com/vapor/vapor/releases/tag/4.69.1): Allow URLEncodedForms to decode 'on' value als Bool => true [Compare Source](https://togithub.com/vapor/vapor/compare/4.69.0...4.69.1) ###### *This patch was authored by [@bobvoorneveld](https://togithub.com/bobvoorneveld) and released by [@Joannis](https://togithub.com/Joannis).* When a HTML form uses a checkbox to check something as a Bool, it sends the 'on' value if checked. The URLEncodedForms decoder should be able to handle that. struct FormData: Decodable { let isActive: Bool } let formData = try req.content.decode(FormData.self) fixes [#2444](https://togithub.com/vapor/vapor/issues/2444) ### [`v4.69.0`](https://togithub.com/vapor/vapor/releases/tag/4.69.0): FileMiddleware: Add convenience support for serving files from a Bundle [Compare Source](https://togithub.com/vapor/vapor/compare/4.68.0...4.69.0) ###### *This patch was authored by [@MrSkwiggs](https://togithub.com/MrSkwiggs) and released by [@Joannis](https://togithub.com/Joannis).* Adds support for instantiating a `FileMiddleware` to serve files from a Bundle. This comes in handy when Vapor is used as a dependency in an `Xcodeproj` and simply passing the `publicDirectory` path is not sufficient. ### [`v4.68.0`](https://togithub.com/vapor/vapor/releases/tag/4.68.0): Enable back deployment of Concurrency [Compare Source](https://togithub.com/vapor/vapor/compare/4.67.5...4.68.0) ###### *This patch was authored by [@sevki](https://togithub.com/sevki) and released by [@0xTim](https://togithub.com/0xTim).* Enable back deployment of Vapor's concurrency APIs on older Apple platforms. This also drops support for Swift versions < 5.5.2 to match SwiftNIO ### [`v4.67.5`](https://togithub.com/vapor/vapor/releases/tag/4.67.5): Prevent vapor streaming requests from randomly losing a first chunk, stalling the request [Compare Source](https://togithub.com/vapor/vapor/compare/4.67.4...4.67.5) ###### *This patch was authored by [@Joannis](https://togithub.com/Joannis) and released by [@0xTim](https://togithub.com/0xTim).* Fixes a bug where a streaming body from a request was not processing a chunk, causing the request to stall. This happened when a handler was being set at the exact moment a chunk was being processed, causing the chunk to be added to a now irrelevant array that was just processed while switching to a streaming callback. See [#2906](https://togithub.com/vapor/vapor/issues/2906) ### [`v4.67.4`](https://togithub.com/vapor/vapor/releases/tag/4.67.4): Fix encoding/decoding an array of dates with URL Encoding [Compare Source](https://togithub.com/vapor/vapor/compare/4.67.3...4.67.4) ###### *This patch was authored and released by [@Joannis](https://togithub.com/Joannis).* Fixes a bug where an Array of Dates wouldn't be encoded or decoded when using URL encoding. ### [`v4.67.3`](https://togithub.com/vapor/vapor/releases/tag/4.67.3): Fix Stream Callback never being called in close [Compare Source](https://togithub.com/vapor/vapor/compare/4.67.2...4.67.3) ###### *This patch was authored and released by [@0xTim](https://togithub.com/0xTim).* Fixes a bug where abandoned requests mean that the stream callback is never invoked. This happens when a client sends a request, the server starts processing it but hasn't constructed the `Response` and then the client closes early. The response is discarded, as is the stream callback so it never gets invoked. This fixes that issue ### [`v4.67.2`](https://togithub.com/vapor/vapor/releases/tag/4.67.2): Fix unused generator parameter in Array.random(count:using:) [Compare Source](https://togithub.com/vapor/vapor/compare/4.67.1...4.67.2) ###### *This patch was authored by [@michal-tomlein](https://togithub.com/michal-tomlein) and released by [@0xTim](https://togithub.com/0xTim).* The `generator` parameter in `Array.random(count:using:)` was unused in what appears to be a copy-paste error. This change passes it down to `FixedWidthInteger.random(using:)`, which was the original intention. ### [`v4.67.1`](https://togithub.com/vapor/vapor/releases/tag/4.67.1): Fix 24h timeformat for `expire` and `last-modified` header [Compare Source](https://togithub.com/vapor/vapor/compare/4.67.0...4.67.1) ###### *This patch was authored by [@patrick-zippenfenig](https://togithub.com/patrick-zippenfenig) and released by [@0xTim](https://togithub.com/0xTim).* `Expire` and `Last-Modified` header were encoding the hour part in 12h format (`hh`) instead of 24h format (`HH`). This results in timestamps being 12 hours off for all afternoon hours. This fixes the format used to follow the [spec](https://httpwg.org/specs/rfc9110.html#field.last-modified) correctly and adds tests to ensure no regressions. ### [`v4.67.0`](https://togithub.com/vapor/vapor/releases/tag/4.67.0): Conforms `Request.Body` to `AsyncSequence` [Compare Source](https://togithub.com/vapor/vapor/compare/4.66.1...4.67.0) ###### *This patch was authored by [@mcritz](https://togithub.com/mcritz) and released by [@0xTim](https://togithub.com/0xTim).* This PR wraps `Request.Body.drain()` as a modern Swift `AsyncSequenceConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.