Repository navigation
Build with Go 1.27.3 and check for known vulnerabilities - #25
Merged
Merged
Conversation
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.
Go 1.27.1 carries a dozen standard-library vulnerabilities that our code reaches, fixed in 1.27.2 and 1.27.3, and golang.org/x/net v0.58.0 has fixed advisories too. This moves to Go 1.27.3 and current golang.org/x modules, after which govulncheck finds no vulnerability the code reaches.
A Vulnerabilities workflow now runs govulncheck on every pull request, every push to main and weekly, so a newly published advisory fails a check even when nothing changed.