Bump golang 1.25.6 to resolve CVEs#437
Conversation
Signed-off-by: Unnati Mishra <[email protected]>
Signed-off-by: Unnati Mishra <[email protected]>
Signed-off-by: Unnati Mishra <[email protected]> Add vendor files Signed-off-by: Unnati Mishra <[email protected]>
758216a to
14bfbd3
Compare
|
Snyk seems to be stuck with original state since 500 error: https://docs.snyk.io/scan-with-snyk/error-catalog?_gl=1*mdputv*_ga*NTMwMzMzMTM3LjE3Njk1NjI3Nzc.*_ga_X9SH3KP7B4*czE3Njk2MjQ0ODYkbzIkZzEkdDE3Njk2MjY4NzQkajYwJGwwJGgw#snyk-9999 even after it should have recovered from the issue: https://status.snyk.io/history In these cases, there are two options, open and close PR OR mark the status as successful: https://docs.snyk.io/scan-with-snyk/pull-requests/pull-request-checks/troubleshoot-pr-checks#mark-as-successful Open and closing PR as seen above did not fix the issue neither did request for retesting it manually from snyk dashboard. So after verifying that the code fixes the claimed vulnerabilities by two different scanners in addition to this comment #437 (comment), I marked the status as successful in SCM as the inherent reason to make this a blocking job has been resolved. Evidence of before and after PR fix: |

Bumping golang +crypto versions to resolve the below CVEs and bump imgpkg to v0.47.1: