ci(scanner): remove vcs information from binary#11935
Conversation
|
Images are ready for the commit at 083baa1. To use with deploy scripts, first |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #11935 +/- ##
=======================================
Coverage 48.07% 48.07%
=======================================
Files 2388 2388
Lines 170869 170869
=======================================
+ Hits 82140 82147 +7
+ Misses 82099 82094 -5
+ Partials 6630 6628 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
8eabe2e to
083baa1
Compare
|
@RTann: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
jvdm
left a comment
There was a problem hiding this comment.
Giving you an approval because the follow ups, if you decide to do them, are likely to be approved as well.
Description
Release vulns again continue to fail. This time it's because of some invalid VCS information in the Go binary. This PR just leaves that out.
User-facing documentation
Testing
Automated testing
How I validated my change
Made this run on my PR prior to merge. Now that NVD API is giving 200s again, looks like it's finally running successfully. https://github.com/stackrox/stackrox/actions/runs/9878607837