chore: add govulncheck and bump Go to 1.20 #523
Merged
Conversation
This file contains 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
Signed-off-by: Radoslav Dimitrov <dimitrovr@vmware.com>
rdimitrov
added
dependencies
Signed-off-by: Radoslav Dimitrov <dimitrovr@vmware.com>
rdimitrov
changed the title
rdimitrov
requested review from
znewman01,
kommendorkapten,
mnm678 and
trishankatdatadog
kommendorkapten
approved these changes
Jul 25, 2023
mnm678
approved these changes
Jul 25, 2023
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.
Description of the changes being introduced by the pull request:
The following PR adds govulncheck to CI.
It also includes a change that narrows the jobs running linters and so on to run on a single OS.
Update:
Updated the version of Go from 1.18 to 1.20 since govulncheck found several vulnerabilities when using the 1.18 version - reference.
Release Notes:
Types of changes:
!, as infeat!: change foo).Please verify and check that the pull request fulfills the following requirements: