v1.1.4

Fixes a cancellation gap introduced in v1.1.3.

On .NET Framework 4.7.2, KlapTransport's HttpWebRequest-based fallback registered HttpWebRequest.Abort() against the caller's CancellationToken, but Abort() does not always promptly unblock an in-flight GetRequestStreamAsync/GetResponseAsync call. As a result, a canceled KLAP request could still block until the request's own configured Timeout elapsed, instead of returning as soon as the token was canceled -- for example, a caller requesting a 20 second cancellation could still see the call block for a much longer runtime-default duration if the request was already in-flight (rather than failing fast on connect).

The net472 fallback now races the underlying GetRequestStreamAsync/GetResponseAsync calls directly against the CancellationToken (via Task.WhenAny) and throws OperationCanceledException immediately once the token fires, independent of whether/when Abort() actually unblocks the original call. The non-net472 HttpClient-based path and TpapTransport were not affected by this specific gap.

Full Changelog: v1.1.3...v1.1.4