fix(deps): update module github.com/quic-go/quic-go to v0.43.0 #251
No reviewers
Labels
No labels
Priority: High
Priority: Low
Priority: Medium
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: sam/awl#251
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/github.com-quic-go-quic-go-0.x"
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:
v0.42.0
->v0.43.0
Release Notes
quic-go/quic-go (github.com/quic-go/quic-go)
v0.43.0
Compare Source
quic-go.net: Launching a new Documentation Site
With this release, we're launching a new documentation site for the quic-go projects (quic-go itself, HTTP/3, webtransport-go, and soon, masque-go): quic-go.net.
The documentation site aims to explain QUIC concepts and how they are made accessible using quic-go's API. This site replaces the wiki, and the ever-growing README files.
A lot of work has gone into the documentation already, but we're by no means done yet. The entire source is public in https://github.com/quic-go/docs/, and we're happy about community contributions.
HTTP Datagrams (RFC 9297)
This release adds support for HTTP Datagrams (RFC 9297), both on the client and on the server side (#4452). HTTP Datagrams are used in WebTransport in CONNECT-UDP (RFC 9298), among others.
The new API for HTTP Datagrams is described on the new documentation page: HTTP Datagrams. The integration of HTTP Datagram support necessitated a comprehensive refactor of the HTTP/3 package, resulting in several breaking API changes listed below.
Breaking Changes
int
instead the internalprotocol.ByteCount
(#4365)Server.SetQuicHeaders
was renamed toSetQUICHeaders
(#4377)Server.QuicConfig
was renamed toQUICConfig
(#4384)RoundTripper.QuicConfig
was renamed toQUICConfig
(#4385)RoundTripOpt.CheckSettings
was removed (#4416). Use the newSingleDestinationRoundTripper
API instead.HTTPStreamer
interface is now implemented by thehttp.ResponseWriter
(and not thehttp.Request.Body
) (#4469)DatagramTooLargeError
(#4470)Other Notable Changes
slog.Logger
(#4449)RoundTrip
errors due to a cancelled context (#4448). Thanks to @GeorgeMac!Context
exposed on thequic.Stream
is now derived from the connection's context (#4414)Clarifications on the QUIC Stream State Machine
Calling CancelWrite after Close
After a long and fruitful discussion (#4404), we decided to clarify that calling
CancelWrite
afterClose
on aSendStream
(or a bidirectional stream) should cause a state transition from the "Data Sent" to the "Reset Sent" state, as described in section 3.1 of RFC 9000. This matches the current behavior of quic-go, however, it didn't match the API documentation (fixed in #4419).This means that stream data will not be delivered reliably if
CancelWrite
is called, and that this applies even ifClose
was called before.Garbage Collection of Streams
This release also changes the way streams are garbage-collected (and the peer is granted additional limit to open a new stream), once they're not needed anymore, in a subtle way:
Thanks to @sukunrt for extremely thorough and helpful reviews on both these PRs!
quic-go needs your support!
Is your project / company relying on quic-go?
Please consider funding the project. Any support is highly appreciated!
Changelog
New Contributors
Full Changelog: https://github.com/quic-go/quic-go/compare/v0.42.0...v0.43.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 Renovate Bot.