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: bump go to 1.18 #9147
chore: bump go to 1.18 #9147
Conversation
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.
I'm not sure why the linter started complaining about these existing lines -- maybe the new indirect
entries in go.mod updated a version of a linter unexpectedly?
+1 to moving to go1.18 anyway.
Seems like a lot of the linting stuff was deprecated in go1.18 |
We are on v1.47.2 of golangci-lint, and v1.47.3 was released two hours ago, including golangci/golangci-lint#3001 to "remove some go1.18 limitations". Shouldn't hurt to update to that newer patch release. |
.golangci.yml
Outdated
@@ -1,7 +1,7 @@ | |||
linters: | |||
enable: | |||
- asciicheck | |||
- bodyclose | |||
# - bodyclose // to be fixed by golangci-lint |
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.
bodyclose support is supposed to be re-enabled as part of golangci-lint v1.47.3, according to golangci/golangci-lint#3001.
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.
New updates still LGTM.
No description provided.