Update Go version to 1.25.11 to address GO-2026-5038 / CVE-2026-42504 - #1129
Open
MaxWinterstein wants to merge 1 commit into
Open
MaxWinterstein wants to merge 1 commit into
MaxWinterstein wants to merge 1 commit into
Conversation
Signed-off-by: Max Winterstein <winterstein@weplan.info>
Member
|
@praveenrewar I tagged you because looks like the problem of the missing image is back, did yll not create a github action to create it? |
Member
I thought we had a github action, but I tried looking for it and could not find anything, and now I think it was just pushed manually a few times before. We should switch to a github action though. |
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
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 this PR does / why we need it:
Updates the Go version to 1.25.11 to address vulnerability GO-2026-5038 aka. CVE-2026-42504 .
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?
Additional Notes for your reviewer:
Review Checklist:
a link to that PR
change
Additional documentation e.g., Proposal, usage docs, etc.: