Changes for version 0.23 - 2026-09-06
- A Fetch::Loop::Standalone inherited across a fork no longer touches the parent's backend, whose kernel object is shared rather than copied. A child exiting with an inherited Fetch deregistered the parent's sockets on epoll and, on io_uring, left the parent submitting stale entries forever.
- A backend inherited across a fork closes no descriptor at destroy: on macOS the dead kqueue's number is already the child's own new kqueue.
- t/28-fork.t.
Modules
HTTP/2 Future-based user agent
store cookies and apply them to requests
a fast, native, Future-compatible async result
ordered, case-insensitive, multi-valued HTTP headers
the event-loop adapter interface Fetch drives
run Fetch under AnyEvent
run Fetch on a Hyperman::Loop
run Fetch on an IO::Async::Loop
Fetch's own vendored C event loop
an HTTP response from Fetch
a live WebSocket connection from Fetch