Skip to content
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

issue when running osv-scanner on project running with golang 1.22 #1123

Closed
felangga opened this issue Jul 16, 2024 · 3 comments · Fixed by #1126 or #1156
Closed

issue when running osv-scanner on project running with golang 1.22 #1123

felangga opened this issue Jul 16, 2024 · 3 comments · Fixed by #1126 or #1156

Comments

@felangga
Copy link

Hello, I have some issues with my project which uses golang v1.22.5.
On the CI, I'm pulling the latest version of OSV-scanner from ghcr.io.

osv-scanner:
    runs-on: xxx
    container: ghcr.io/google/osv-scanner:v1.8.2
        ....

I got this error when running the osv-scanner, does it because the osv-scanner was built using go v1.21?

This application uses version go1.21 of the source-processing packages but runs version go1.22 of 'go list'. It may fail to process source files that rely on newer language features. If so, rebuild the application using a newer version of Go.
@oliverchang
Copy link
Collaborator

@another-rex and @hogo6002 , do we just need another Go upgrade here?

@another-rex
Copy link
Collaborator

Yes, ideally we want to have our binary be built by the latest version of golang, but keep our library compatible with the previous version.

@spencerschrock
Copy link
Contributor

Yes, ideally we want to have our binary be built by the latest version of golang, but keep our library compatible with the previous version.

Is the use of stable and oldstable setup-go aliases worth checking out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants