-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/vuln: govulncheck v1.0.2 doesn't support workspaces anymore #65130
Comments
Yes, this seems related. We are working on it. |
I've put a repro in my duplicate #65155 if it helps - any workaround meanwhile? [well I guess I can pin my action to 1.0.1 instead of latest] |
Change https://go.dev/cl/556775 mentions this issue: |
We just merged a hotfix for folks with a go.work file - would you both be able to recreate the same steps with A proper/cleaner fix which will also address those using vendor directories will be merged and a new version with the fixes will be tagged and released by Monday. |
@maceonthompson yes it worked, thanks a lot https://github.com/fortio/fortiotel/actions/runs/7576563961/job/20635661749
might be worth making that 1.0.3 though? |
current master works, thank you very much |
@ldemailly apologies for the delay - 1.0.3 is being tagged currently and we expect it to be released today/tomorrow. |
v1.0.3 tag is available now. |
in a repo with a
go.work
file:might be since this change https://go.googlesource.com/vuln/+/61b4508dba3bfb2ddc378c5f84bedfa3a544b0b7%5E%21/internal/vulncheck/packages.go
v1.0.1 does not have this problem.
might be related to #65124
The text was updated successfully, but these errors were encountered: