-
Notifications
You must be signed in to change notification settings - Fork 66
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
chore: update to Go 1.21 #402
Conversation
@@ -10,4 +10,5 @@ jobs: | |||
- name: golangci-lint | |||
uses: reviewdog/action-golangci-lint@v2 | |||
with: | |||
go_version_file: "go.mod" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: reviewdog uses snake case for its arguments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gonna be honest, don't really understand these changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might change between go versions, but should be backwards and forwards compatible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Didn't know about the go-version-file, makes it easier to have versioned updated of the go toolchain. Even though it's generally not a problem 😄
Included in release v0.48.0 🎉 |
What does this change
Updates build to use Go 1.21, and tries to ensure CI workflows are operating against the version of Go currently used by
go.mod
.Go 1.21 includes various enhancements including new APIs for
slice
, along with a variety of fixes.What issue does it fix
No specific issue, just looking to be able to use some newer APIs.
Notes for the reviewer
Some of the workflows only execute on
master
. The changes appear safe, and any issues could potentially be fixed in a "fast follow" response.Checklist