Skip to content

fix: upgrade klone, vendor govulncheck workflow#682

Merged
SgtCoDFish merged 1 commit into
masterfrom
govulncheck-fix-2
Aug 8, 2025
Merged

fix: upgrade klone, vendor govulncheck workflow#682
SgtCoDFish merged 1 commit into
masterfrom
govulncheck-fix-2

Conversation

@SgtCoDFish
Copy link
Copy Markdown
Contributor

@SgtCoDFish SgtCoDFish commented Aug 7, 2025

I'd mistakenly thought that govulncheck respected GOPRIVATE from local testing, but I'd actually set up an environment where govulncheck had access to the private dependency I was trying to avoid and as such it had passed locally and started to fail in CI.

This PR:

  1. Incorporates the contents of Revert #315, add skip for govulncheck cert-manager/makefile-modules#317
  2. Disables upstream govulncheck
  3. Makes some changes to the newly vendored govulncheck job so it runs

@SgtCoDFish SgtCoDFish force-pushed the govulncheck-fix-2 branch 5 times, most recently from 64b3cdd to 20f149a Compare August 7, 2025 15:11
@SgtCoDFish SgtCoDFish changed the title fix: upgrade klone and set goprivate for private dependency fix: upgrade klone, vendor govulncheck workflow Aug 7, 2025
@SgtCoDFish
Copy link
Copy Markdown
Contributor Author

/hold

WIP until cert-manager/makefile-modules#317 merges

Copy link
Copy Markdown
Contributor

@wallrj-cyberark wallrj-cyberark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you ran govulncheck workflow on this branch and it passed

image

https://github.com/jetstack/jetstack-secure/actions/workflows/govulncheck.yaml

But the nightly master version also seems to be passing so I might be misunderstanding what the problem is:

image

@SgtCoDFish
Copy link
Copy Markdown
Contributor Author

Looks like you ran govulncheck workflow on this branch and it passed

I did, but the klone.yaml is still pointing at my fork - I'll repoint at the upstream makefile-modules!

It seems difficult to stop govulncheck attempting to pull and analyse
private dependencies. We still want to run it, so the simplest thing to
do is diverge from upstream makefile-modules and maintain the
govulncheck workflow by hand in this repo.

This requires changes to the govulncheck workflow itself, and means we
have to disable the upstream govulncheck targets and copy them locally.

Signed-off-by: Ashley Davis <ashley.davis@cyberark.com>
@SgtCoDFish SgtCoDFish merged commit 699a653 into master Aug 8, 2025
2 checks passed
@SgtCoDFish SgtCoDFish deleted the govulncheck-fix-2 branch August 8, 2025 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants