go.mod: raise go directive to 1.26.4#245
Merged
Merged
Conversation
Addresses GO-2026-5039 and GO-2026-5037 flagged by govulncheck. Given the limited downstream use of our module it seemed preferable to bump the go directive vs using a toolchain directive.
botovq
approved these changes
Jun 3, 2026
Member
Author
|
Theo: Thanks for the quick review :-) Given this is breaking CI for external contributors I'm going to merge now but will commit to more iteration if any other feedback arrives. |
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.
Addresses GO-2026-5039 and GO-2026-5037 flagged by govulncheck in CI.
Given the limited downstream use of our module it seemed preferable to bump the
godirective vs using atoolchaindirective but I'm open to revisiting this.