chore(deps): update dependency hackney to v4.6.1 #61
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.5.2→4.6.1Release Notes
benoitc/hackney (hackney)
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.v4.6.0Compare Source
Added
set_owner/2now works while a response body is streaming, in both the synchronous and the async path. It used to return{error, invalid_state}once the body had started. This lets a short lived worker run a request and hand the still streaming response to a longer lived process before it exits, without stopping the connection.connect/4accepts a binary host, restoring the 1.x behavior. A binary is converted to a string, so callers passing a binary host no longer fail.Fixed
no_reusefor proxy tunnels, SSL upgrades or a disabled pool, or answered withConnection: close) is now closed and its process stopped when a synchronous request completes, instead of parking inconnectedforever. With a long lived owner nothing stopped it, so onehackney_connprocess leaked per request until the node ran out of memory (#902). The sync and async reuse decision now share the same check, which also stops ano_reusepooled connection on the async path.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.6.0to chore(deps): update dependency hackney to v4.6.1