-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 add osv-scanner config for correcting go version used #695
base: main
Are you sure you want to change the base?
🌱 add osv-scanner config for correcting go version used #695
Conversation
/cc @kashifest |
570a9a1
to
9e6275e
Compare
9e6275e
to
4022c4b
Compare
/retest |
8ac994a
to
4a40b8c
Compare
Signed-off-by: Tuomo Tanskanen <tuomo.tanskanen@est.tech>
4a40b8c
to
257a719
Compare
Removed test triggers etc, should be final version. See TODO for release branches in some later PR. |
/override metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
@tuminoid: Overrode contexts on behalf of tuminoid: metal3-centos-e2e-integration-test-main, metal3-ubuntu-e2e-integration-test-main In response to this:
Instructions 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. |
/cc @kashifest @lentzi90 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Use OSV scanner config, that sets the used go version manually, instead of osv-scanner detecting it from go.mod, which is not correct way for us. Go version from go.mod is not user-friendly way of bumping Go as it forced everyone downstream to use that Go version or newer, forcing unwanted toolchain bumps.
It also changes the reporter action to not fail if there are vulns, we want to get the vulns into Security tab, and failing a scan should mean the scan action itself had issue.
TODO items for later PRs: