feat: add govulncheck for checking whether ArgoCD has CVE#21928
feat: add govulncheck for checking whether ArgoCD has CVE#21928sivchari wants to merge 1 commit into
Conversation
❗ Preview Environment undeploy from Bunnyshell failedSee: Environment Details | Pipeline Logs Available commands (reply to this comment):
|
|
https://github.com/argoproj/argo-cd/actions/runs/13448667288/job/37579098493?pr=21928 This CI is passed when #21929 is merged. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #21928 +/- ##
==========================================
+ Coverage 55.95% 56.04% +0.09%
==========================================
Files 343 343
Lines 57327 57536 +209
==========================================
+ Hits 32075 32248 +173
- Misses 22619 22645 +26
- Partials 2633 2643 +10 ☔ View full report in Codecov by Sentry. |
ff0db36 to
024b8c9
Compare
|
When argoproj/gitops-engine#698 is merged, we can deal with issue that CI is failed. |
bb5c3b7 to
358d4ec
Compare
358d4ec to
4f5154a
Compare
|
@andrii-korotkov-verkada |
|
@crenshaw-dev @gdsoumya |
|
https://pkg.go.dev/vuln/GO-2025-3547 is occurred, but this issue hasn't been resolved yet. |
Signed-off-by: sivchari <shibuuuu5@gmail.com>
4f5154a to
0db092d
Compare
Checklist:
I added govulncheck workflow to check whether ArgoCD has CVE.