fix vulns 2025-05 - #338
Merged
Merged
Conversation
troy-chuang
force-pushed
the
fix-vulns-2026-05
branch
from
May 29, 2026 00:35
9f31436 to
6f095db
Compare
troy-chuang
force-pushed
the
fix-vulns-2026-05
branch
from
May 29, 2026 00:57
6f095db to
d47254b
Compare
troy-chuang
marked this pull request as ready for review
May 29, 2026 18:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Bump golang.org/x/net to v0.55.0 to patch CVE-2026-39821.
Update Makefile and CI workflows for go version bump required by the package upgrade.
Where should the reviewer start?
go.mod
How should this be manually tested?
Collected metrics data using both the new and current production versions.
Analyze that we produced equivalent content.
Any background context you want to provide?
What picture best describes this PR (optional but encouraged)?
What are the relevant Github Issues?
Developer Done List
For the Reviewer:
By approving this PR, the reviewer acknowledges that they have checked all items in this done list.
Reviewer/Approval Done List