Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses to this mail must be
sent to the mailing list.
Last release 3.4.7 was issued on 2026-10-14. There are currently 51
patches in the queue cut down this way:
- 3 MAJOR, first one merged on 2026-10-20
- 23 MEDIUM, first one merged on 2026-10-20
- 25 MINOR, first one merged on 2026-10-20
Thus the computed ideal release date for 3.4.8 would be 2026-11-03, which was
one week ago.
Last release 3.3.17 was issued on 2026-10-14. There are currently 1
patches in the queue cut down this way:
- 1 MEDIUM, first one merged on 2026-10-21
Thus the computed ideal release date for 3.3.18 would be 2026-11-20, which is
in two weeks or less.
Last release 3.2.26 was issued on 2026-10-14. There are currently 1
patches in the queue cut down this way:
- 1 MEDIUM, first one merged on 2026-10-21
Thus the computed ideal release date for 3.2.27 would be 2026-12-20, which is
in six weeks or less.
Last release 3.0.30 was issued on 2026-10-14. There are currently 1
patches in the queue cut down this way:
- 1 MEDIUM, first one merged on 2026-10-21
Thus the computed ideal release date for 3.0.31 would be 2027-01-19, which is
in ten weeks or less.
The current list of patches in the queue is:
- 3.4 - MAJOR : mux-quic: do not crash on connection
error after glitch threshold
- 3.4 - MAJOR : mux-h2: split absolute URIs like the
HTTP analysers do on output
- 3.4 - MAJOR : mux-quic: do not crash on connection
error after glitch threshold"
- 3.4 - MEDIUM : h3: split absolute URIs like the HTTP
analysers do on output
- 3.4 - MEDIUM : bwlim: never burst more than the
pending data in input
- 3.4 - MEDIUM : mux-h1: Don't close the connection on
a payload parsing error
- 3.4 - MEDIUM : h1: make the Connection/Upgrade
headers cleanup idempotent
- 3.4 - MEDIUM : mux-h1: don't stall when draining more
than a buffer of data
- 3.4 - MEDIUM : mux-h1: don't lose error responses
once a content-length was parsed
- 3.4 - MEDIUM : h1-htx: don't stall on messages ending
exactly at the buffer's end
- 3.4 - MEDIUM : h3: fix BUG_ON() crash with glitch
after QPACK dec err
- 3.4 - MEDIUM : mux-h1: don't spread-close idle conns
with idle-close-on-response
- 3.4 - MEDIUM : mux-h1: don't truncate responses on
soft-stop
- 3.4 - MEDIUM : stats-file: shm-stats-file be counters
not working anymore
- 3.4 - MEDIUM : mux-h1: don't swap buffers when
transferring data with a reserved offset
- 3.4 - MEDIUM : h3: fix BUG_ON() crash with glitch on
SETTINGS parsing
- 3.4 - MEDIUM : h3: fix BUG_ON() crash with glitch on
GOAWAY parsing
- 3.4 - MEDIUM : mux-h1: don't lose the end of the
previous chunk in h1_make_chunk()
- 3.4 - MEDIUM : mux-h1: don't truncate the response
when closing after draining
- 3.4 - MEDIUM : mux-h1: don't send chunked responses
to HTTP/1.0 clients
- 3.4 - MEDIUM : peers: keep the earliest sync task
deadline
- 3.4 - MEDIUM : resolvers: reject too long labels when
encoding a name
- 3.4 - MEDIUM : cli: Fix parsing of big payloads with
dynamically allocated buffer
- 3.0, 3.2, 3.3, 3.4 - MEDIUM : task: do not destroy twice the
tasks already killed in mworker_cleantasks()
- 3.4 - MEDIUM : quic: use datagram destination as
source for Retry
- 3.4 - MEDIUM : h1: don't rewrite the Upgrade header
when not cleaning headers
- 3.4 - MINOR : quic: use datagram destination as
source for version negotiation
- 3.4 - MINOR : h1: keep accepting unsafe violations
after a parser reset
- 3.4 - MINOR : mux-h1: don't dereference a NULL
opposite sedesc in h1_fastfwd()
- 3.4 - MINOR : mux-h1: only rely on the client's
method for bodyless responses
- 3.4 - MINOR : check: do not inspect errno if conn
FDLESS
- 3.4 - MINOR : mux-h1: fix the open streams counter
on stream creation failure
- 3.4 - MINOR : mux-h1: only reset the session's
timing info on the frontend side
- 3.4 - MINOR : mux_quic: do not crash on SE_SHR_DRAIN
shut
- 3.4 - MINOR : mux-h1: search the websocket key in
the right message
- 3.4 - MINOR : h1: forget a previous pass' results
when parsing headers only
- 3.4 - MINOR : mux-h1: reset the
content-length/chunking state after a 1xx response
- 3.4 - MINOR : sample: Fix wrong 'base64urldec'
return value check in 'jwt_member_query'
- 3.4 - MINOR : quic: use datagram destination as
source for stateless reset
- 3.4 - MINOR : h3: fix BUG_ON() crash with glitch on
htx_set_eom() failure
- 3.4 - MINOR : mux-h1: don't keep fast-forwarding
disabled for the next streams
- 3.4 - MINOR : mux_quic: prevent RS/SS on unistream
with hq-interop
- 3.4 - MINOR : quic: handle EINTR on emission of
packets without connection
- 3.4 - MINOR : h3: fix risk of BUG_ON() crash with
glitch on unknown frame
- 3.4 - MINOR : mux-h1: don't forward request trailers
named like server name header
- 3.4 - MINOR : h1: don't use uninitialized start line
pointers when restarting
- 3.4 - MINOR : mux-h1: convert the
- 3.4 - MINOR : mux-h1: Don't subscribe for receives
once read0 or error received
- 3.4 - MINOR : mux-h1: don't report a 408 error on
timeout of a closed connection
- 3.4 - MINOR : quic: valid NEW_TOKEN connections are
counted as half-open
- 3.4 - MINOR : mux-h1: report payload parsing
glitches to the session
--
The haproxy stable-bot is freely provided by HAProxy Technologies to help
improve the quality of each HAProxy release. If you have any issue with these
emails or if you want to suggest some improvements, please post them on the
list so that the solutions suiting the most users can be found.
