fix(deps): update module github.com/quic-go/quic-go to v0.50.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/quic-go/quic-go	v0.49.0 -> v0.50.0

---

Release Notes

quic-go/quic-go (github.com/quic-go/quic-go)

v0.50.0

Compare Source

This release implements server-side path-probing (as described in section 9 of RFC 9000): #​4932, #​4933, #​4935, #​4938, #​4939, #​4940, #​4941, #​4944, #​4947, #​4959.

When the server receives a packet for an existing connection from a different IP address / port, it first needs to probe the new path before it can send packets on that path. This happens when the client experiences a NAT rebinding, and when the client attempts to migrate to a new connection. Previous versions of quic-go would accept the packets from the new path, but never switch to the new path.

Note that the client side connection migration logic (#​234) is not yet implemented in quic-go (but we're working on it!).

Major Changes

• use the new crypto/tls 0-RTT API that we helped design in 2023: #​4953
• use a ringbuffer to store received packets, significantly reducing memory consumption: #​4929
• according to our Go version policy, we removed support for Go 1.22. quic-go now requires Go 1.23 or Go 1.24: #​4880
• the connection timer logic was refactored, enabling future changes to this code path: #​4927

Other Fixes

• fix busy-looping when pacing packets and the send queue blocks: #​4943
• don't drop undecryptable packets when deriving 2 sets of keys at the same time (i.e. when resuming a 0-RTT connection): #​4950

Go 1.24 FIPS 140-3 Caveats

Go 1.24 made several changes related to FIPS 140-3 compliance. Among others, it introduced a fips-only mode (enabled by setting GODEBUG="fips140=only").

It is not possible to use quic-go in fips-only mode, since the QUIC RFC requires initializing an AES GCM cipher with a fixed nonce, which is considered unsafe according to FIPS 140-3, or at least the Go team's interpretation thereof. See https://github.com/quic-go/quic-go/issues/4894 and the discussion on Go issue #​69536.

Before v0.50.0, quic-go would initialize the AES cipher on init, leading to a panic when using fips-only mode. For v0.50.0 we changed this behavior to lazy initialization (https://github.com/quic-go/quic-go/pull/4916). Note that this still means it's not possible to use QUIC in fips-only mode.

Changelog

• ackhandler: remove unneeded error return from packet history iterator by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4917
• proxy: remove Proxy.LocalPort method by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4920
• proxy: rename to Proxy, refactor initialization by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4921
• proxy: add function to simulate NAT rebinding by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4922
• proxy: optimize packet sorting logic by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4923
• simplify handling of packet unpacking errors by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4924
• refactor connection error propagation by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4925
• refactor packet handling into a separate function by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4926
• congestion: migrate the pacer tests away from Ginkgo by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4929
• utils: add a method to reset the RTTStats for connection migration by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4930
• add a packet packer method to pack path probe packets by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4932
• add a method to change the remote address of the sendConn by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4933
• ackhandler: add path probe tracking logic to sent packet history by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4934
• implement connection ID handling for path probe packets by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4935
• fix flaky TestConnectionReceivePrioritization by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4936
• add a method to the sendQueue to send probe packets by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4939
• implement a path manager to track the validation status of new paths by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4938
• query MTU discoverer for increases after processing ACK frame by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4941
• http3: minor simplification of panic handling logic by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4942
• use a ringbuffer to store received packets in the connection by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4928
• refactor connection timer logic by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4927
• ackhandler: implement timer logic for path probe packets by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4940
• fix busy-looping when pacing and the send queue blocks by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4943
• add a way to reset the MTU discoverer by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4947
• migrate the connection ID generator tests away from Ginkgo by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4948
• implement server-side path validation logic by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4944
• keep undecryptable packets when deriving 0-RTT and handshake keys by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4950
• ci: update golangci-lint to v1.64.4 by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4951
• bump go.mod version to Go 1.23, run 1.23 and 1.24 on CI by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4880
• ackhandler: use Go iterators to iterate over sent packets by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4952
• handshake: use new crypto/tls 0-RTT API by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4953
• ackhandler: fix handling of lost path probes on loss timer by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4956
• remove unneeded tracking of acknowledgments for PATH_CHALLENGEs by @​marten-seemann in https://github.com/quic-go/quic-go/pull/4959

Full Changelog: quic-go/quic-go@v0.49.0...v0.50.0

---

Configuration

📅 Schedule: 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 was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.22 -> 1.24.1

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.