Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update quic-go to 0.42.0 for CVE-2024-22189 #1541

Merged
merged 1 commit into from
Apr 16, 2024

Conversation

dfarrell07
Copy link
Member

@dfarrell07 dfarrell07 commented Apr 15, 2024

Generated by:

go get github.com/quic-go/[email protected]
go get toolchain@none
go mod tidy

@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr1541/dfarrell07/quic_16
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

Generated by:

go get github.com/quic-go/[email protected]
go get toolchain@none
go mod tidy

Signed-off-by: Daniel Farrell <[email protected]>
@dfarrell07
Copy link
Member Author

dfarrell07 commented Apr 15, 2024

I'm not sure about the best way to handle the new-ish toolchain directive. It would be added by this bump, as this quic-go update requires golang 1.21 which adds the feature by default. However, the toolchain would be set to my local golang version, which seems pretty arbitrary. That would force go commands for this repo to use my version. It should happen seamlessly behind the scenes, but it still seems undesirable to set an arbitrary constraint.

https://go.dev/blog/toolchain
https://go.dev/doc/toolchain

@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Apr 16, 2024
@tpantelis tpantelis enabled auto-merge (rebase) April 16, 2024 13:59
@tpantelis tpantelis merged commit 3d50883 into submariner-io:release-0.16 Apr 16, 2024
28 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr1541/dfarrell07/quic_16]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-test When a PR is ready for full E2E testing security
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants