Handle GOEXPERIMENTs in go version #2893
Merged
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.
See anchore/grype#1851 for more context.
I was originally going to put this into
scanFile
, but the existing tests made it a little easier to test if I did it inparse_go_binary.go
instead.I've also tested this manually, before:
And after:
I can also confirm that after modifying
grype
to use my branch, it no longer emits a warning:Interestingly,
grype
still picks up these CVEs even without my change, so maybe this warning isn't all that necessary? I don't have a super firm grasp on how this works.