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

chore: bump go to 1.18 #9147

Merged
merged 13 commits into from Aug 1, 2022
Merged

chore: bump go to 1.18 #9147

merged 13 commits into from Aug 1, 2022

Conversation

cmwaters
Copy link
Contributor

@cmwaters cmwaters commented Aug 1, 2022

No description provided.

@cmwaters cmwaters requested a review from ebuchman as a code owner August 1, 2022 13:07
@cmwaters cmwaters requested a review from a team August 1, 2022 13:07
Copy link
Contributor

@mark-rushakoff mark-rushakoff left a 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.

@cmwaters
Copy link
Contributor Author

cmwaters commented Aug 1, 2022

level=warning msg="[linters context] gosimple is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649."
  level=warning msg="[linters context] staticcheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649."
  level=warning msg="[linters context] structcheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/26[49](https://github.com/tendermint/tendermint/runs/7612082007?check_suite_focus=true#step:5:51)."
  level=warning msg="[linters context] stylecheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649."
  level=warning msg="[linters context] unused is disabled because of go1.18. You can track the evolution of the go1.18 support by following the https://github.com/golangci/golangci-lint/issues/2649."

Seems like a lot of the linting stuff was deprecated in go1.18

@mark-rushakoff
Copy link
Contributor

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
Copy link
Contributor

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.

Copy link
Contributor

@mark-rushakoff mark-rushakoff left a 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.

@cmwaters cmwaters merged commit 1e9d81f into main Aug 1, 2022
@cmwaters cmwaters deleted the cal/go1.18 branch August 1, 2022 14:45
samricotta pushed a commit that referenced this pull request Aug 1, 2022
samricotta pushed a commit that referenced this pull request Aug 1, 2022
samricotta pushed a commit that referenced this pull request Aug 1, 2022
cmwaters added a commit that referenced this pull request Aug 8, 2022
samricotta pushed a commit that referenced this pull request Aug 16, 2022
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.

None yet

2 participants