Pin CLI releases to Go 1.25.13 - #159
Merged
Merged
Conversation
LukaszMarchewka
approved these changes
Aug 17, 2026
LukaszMarchewka
approved these changes
Aug 17, 2026
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.
Pin the release build to fixed Go 1.25.13 through
go.mod, make every setup-go job consume that file, and update the local development toolchain. A new CLI tag after merge will replace vulnerable v3.3.7.Tracking: https://github.com/StackVista/cve-reporter/issues/32
Validation:
go test ./...; release-style binary built withGOTOOLCHAIN=go1.25.13reportsgo1.25.13.