SpaceAge/space_age_api
Watch
2
0
Fork
You've already forked space_age_api
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

chore(deps): update dependency hackney to v4.8.4 #86

Open
MaidFox wants to merge 1 commit from renovate/hackney-4.x-lockfile into main
pull from: renovate/hackney-4.x-lockfile
merge into: SpaceAge:main
Conversation 0 Commits 1 Files changed 2 +3 -3
MaidFox commented 2026-09-27 06:44:11 -07:00
Member
Copy link

This PR contains the following updates:

Package Type Update Change
hackney (source) prod patch 4.8.2 → 4.8.4

Release Notes

benoitc/hackney (hackney)

v4.8.4: hackney 4.8.4

Compare Source

Fixed
  • hackney:close/1 on a shared pooled HTTP/2 connection resets only the
    caller's own streams. It stopped the connection, failing every other
    caller's streams on it. The connection still closes itself once idle with
    no stream open.
  • A connection opened without a pool honours connect_timeout above 8
    seconds, and a dial that outlives it returns {error, connect_timeout}.
    The wait was capped at 8 seconds and ended as an exit in the caller. A
    dial stuck in the transport no longer holds the caller past its deadline
    either (#​945).

v4.8.3: hackney 4.8.3

Compare Source

Fixed
  • hackney_conn:set_owner/2 works while a streamed request body is being
    sent. It returned {error, invalid_state}.
  • A response body cut short by the server closing the connection is an
    error. For a chunked or Content-Length body, body/1 returns
    {error, {closed, Partial}} with the bytes that arrived, and
    stream_body/1 and async responses end with {error, closed}. They
    reported a short body as complete. A body with neither still ends when the
    connection closes.
  • An HTTPS request through a CONNECT proxy reached over TLS
    ({proxy_transport, ssl}) works. The target TLS handshake ran over the
    proxy TLS socket as if it were plain TCP and failed.
  • A pooled connection from hackney:connect/* stays with its caller between
    requests, and hackney:close/1 checks it back into the pool. It went back
    to the pool after every response while the caller still used it, so the
    pool could stop it in the middle of the next request ({error, closed})
    or lend it to another process.

Configuration

📅 Schedule: (UTC)

  • 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 CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [hackney](https://hex.pm/packages/hackney) ([source](https://github.com/benoitc/hackney)) | prod | patch | `4.8.2` → `4.8.4` | --- ### Release Notes <details> <summary>benoitc/hackney (hackney)</summary> ### [`v4.8.4`](https://github.com/benoitc/hackney/releases/tag/4.8.4): hackney 4.8.4 [Compare Source](https://github.com/benoitc/hackney/compare/4.8.3...4.8.4) ##### Fixed - `hackney:close/1` on a shared pooled HTTP/2 connection resets only the caller's own streams. It stopped the connection, failing every other caller's streams on it. The connection still closes itself once idle with no stream open. - A connection opened without a pool honours `connect_timeout` above 8 seconds, and a dial that outlives it returns `{error, connect_timeout}`. The wait was capped at 8 seconds and ended as an exit in the caller. A dial stuck in the transport no longer holds the caller past its deadline either ([#&#8203;945](https://github.com/benoitc/hackney/issues/945)). ### [`v4.8.3`](https://github.com/benoitc/hackney/releases/tag/4.8.3): hackney 4.8.3 [Compare Source](https://github.com/benoitc/hackney/compare/4.8.2...4.8.3) ##### Fixed - `hackney_conn:set_owner/2` works while a streamed request body is being sent. It returned `{error, invalid_state}`. - A response body cut short by the server closing the connection is an error. For a chunked or `Content-Length` body, `body/1` returns `{error, {closed, Partial}}` with the bytes that arrived, and `stream_body/1` and async responses end with `{error, closed}`. They reported a short body as complete. A body with neither still ends when the connection closes. - An HTTPS request through a CONNECT proxy reached over TLS (`{proxy_transport, ssl}`) works. The target TLS handshake ran over the proxy TLS socket as if it were plain TCP and failed. - A pooled connection from `hackney:connect/*` stays with its caller between requests, and `hackney:close/1` checks it back into the pool. It went back to the pool after every response while the caller still used it, so the pool could stop it in the middle of the next request (`{error, closed}`) or lend it to another process. </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMTUuMTAiLCJ1cGRhdGVkSW5WZXIiOiI0NC4xMTUuMTAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
chore(deps): update dependency hackney to v4.8.4
All checks were successful
Lint / Lint (pull_request) Successful in 1m19s
Details
Nix check / check-nix (pull_request) Successful in 1m45s
Details
1d2417bd6d
MaidFox force-pushed renovate/hackney-4.x-lockfile from 1d2417bd6d
All checks were successful
Lint / Lint (pull_request) Successful in 1m19s
Details
Nix check / check-nix (pull_request) Successful in 1m45s
Details
to 4b08fb6fa2
All checks were successful
Lint / Lint (pull_request) Successful in 2m4s
Details
Nix check / check-nix (pull_request) Successful in 2m54s
Details
2026-09-28 06:45:43 -07:00 Compare
All checks were successful
Lint / Lint (pull_request) Successful in 2m4s
Details
Nix check / check-nix (pull_request) Successful in 2m54s
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/hackney-4.x-lockfile:renovate/hackney-4.x-lockfile
git switch renovate/hackney-4.x-lockfile

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/hackney-4.x-lockfile
git switch renovate/hackney-4.x-lockfile
git rebase main
git switch main
git merge --ff-only renovate/hackney-4.x-lockfile
git switch renovate/hackney-4.x-lockfile
git rebase main
git switch main
git merge --no-ff renovate/hackney-4.x-lockfile
git switch main
git merge --squash renovate/hackney-4.x-lockfile
git switch main
git merge --ff-only renovate/hackney-4.x-lockfile
git switch main
git merge renovate/hackney-4.x-lockfile
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SpaceAge/space_age_api!86
No description provided.