Repository navigation
Build with Go 1.26.10 and check for known vulnerabilities - #43
Merged
Merged
Conversation
Releases set Go from go.mod and were building with Go 1.25, which no longer receives security fixes.
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.
Releases set Go from
go.mod, which saidgo 1.25, so they were building with Go 1.25. That release line no longer receives security fixes.toolchain go1.26.10pins the newest supported patch, and thego 1.25minimum stays as it is.CI now runs
govulncheck, so a stale toolchain or a flawed dependency fails the check.Builds from the Nix flake still use the Go in the nixpkgs lock.