SwiftNIO HTTP/2 1.13.0

Notable Changes

The release contains a fix for an ergonomic issue which could result in a connection error when first writing on streams in an order different to the order in which they were created. The issue is detailed in #214 and associated pull requests.

The fix required that HTTP/2 stream channels created by the local peer be assigned stream IDs when they first emit writes rather than when they are initialized. As such, HTTP/2 stream channels will now operate on HTTP2Frame.FramePayload when created using the new API. The old behaviour, where stream channels operate on HTTP2Frame, remains but is now deprecated.

The following functions were deprecated and replaced with equivalents which do not accept an HTTP2StreamID in the stream initializer closure:

• HTTP2StreamMultiplexer.init,
• HTTP2StreamMultiplexer.createStreamChannel,
• Channel.configureHTTP2Pipeline,

In addition, the HTTP2 to HTTP1 codecs were also deprecated:

• HTTP2ToHTTP1ClientCodec is deprecated in favor of HTTP2FramePayloadClientCodec
• HTTP2ToHTTP1ServerCodec is deprecated in favor of HTTP2FramePayloadServerCodec

SemVer Minor

• Fixed an ergonomics issue which could result in a connection error when writing on streams in an order different to their creation order (#215, #216, #217, #218, #219, #221, #222, #224, #225, #226, #227, #228).

Other Changes

• Various changes to CI and testing (#211, #212, #223)