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

Specify full golang toolchain version #15

Merged
merged 1 commit into from
Jun 24, 2024

Conversation

vitaliyf
Copy link
Contributor

CodeQL is warning about:

As of Go 1.21, toolchain versions must use the 1.N.P syntax.
1.22 in go.mod does not match this syntax and there is no additional toolchain directive, which may cause some go commands to fail.

CodeQL is [warning](https://github.com/embrace-io/s3-batch-object-store/security/code-scanning/tools/CodeQL/status/configurations/automatic) about:
> As of Go 1.21, toolchain versions [must use the 1.N.P syntax](https://go.dev/doc/toolchain#version).
> 1.22 in go.mod does not match this syntax and there is no additional toolchain directive, which may cause some go commands to fail.
@vitaliyf vitaliyf self-assigned this Jun 22, 2024
Copy link
Collaborator

@pablomatiasgomez pablomatiasgomez left a comment

Choose a reason for hiding this comment

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

Interesting that this is working now, when I tested this a few commits ago, I got an error from GHA https://github.com/embrace-io/s3-batch-object-store/actions/runs/9319220557/job/25653261726 Maybe it was because at that point I was using actions/setup-go@v4 and now we are in v5.

@vitaliyf
Copy link
Contributor Author

In that build you were compiling using go 1.20

@vitaliyf vitaliyf merged commit 55980d3 into master Jun 24, 2024
3 checks passed
@vitaliyf vitaliyf deleted the vitaliyf/go-mod-toolchain-version branch June 24, 2024 13:16
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