chore(deps): update dependency hackney to v4.7.2 #62
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/hackney-4.x-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
4.6.0→4.7.2Release Notes
benoitc/hackney (hackney)
v4.7.2Compare Source
Bump
quicto 1.7.1. A clean QUIC connection close (idle pooled HTTP/3 connections, orderly shutdown) no longer emits ERROR and CRASH reports fromquic_h3_connectionnor propagates an abnormal exit to the connection owner. This also removes the intermittent eunit group cancellation in the h3/wt test suites.See NEWS.md for details. PR #913.
v4.7.1Compare Source
Chunked decoding no longer fails with
{error, invalid_chunk_size}when the CRLF terminating a chunk-size line is split across two socket reads (buffer ending on a lone\r). The parser now waits for the\n(#901).A malformed chunk-size line or chunk terminator now fails cleanly with
{error, invalid_chunk_size}or{error, poorly_formatted_chunked_size}instead of crashing the parser with acase_clauseerror.See NEWS.md for details. PR #912.
v4.7.0Compare Source
HTTP/2 request bodies larger than the peer's flow control window no longer fail with
{error, send_buffer_full}. Body sends block until the server opens the window, bounded by the newsend_timeoutoption (default 30000 ms,infinityallowed,nonblockrestores the old fail-fast behavior). If the window never opens the request fails with{error, timeout}and the abandoned stream is reset so its buffered body does not linger on a shared connection. Applies to whole-body and streamed HTTP/2 request bodies; HTTP/1.1 and HTTP/3 are unchanged.HTTP/2 async requests now deliver their response messages: the stream entry stored an internal reference where the delivery code expected the
stream_topid, so every async HTTP/2 response was silently dropped.HTTP/2
{async, once}now honorsstream_next/1with the same contract as HTTP/1.1: status and headers eagerly, then one message per pull. once streams use h2 manual flow control, so a slow consumer keeps the peer's window closed and in-flight data stays bounded to one window.Connections created with
hackney:connect/4and{pool, false}honor a{send_timeout, T}connect option; pooled connections keep the default and take the per-request option instead.See NEWS.md for details. PR #911.
v4.6.1Compare Source
Changed
h2to 0.11.0. It addsh2:peername/1, which returns the peer's{IpAddress, Port}for a live connection. Additive only; no behavior change for hackney.Configuration
📅 Schedule: (UTC)
🚦 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.
chore(deps): update dependency hackney to v4.7.1to chore(deps): update dependency hackney to v4.7.2