-
Notifications
You must be signed in to change notification settings - Fork 275
[release-0.9] Bump golangci-lint #2619
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
base: release-0.9
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Golangci-lint v1.64 is the first one to support go 1.24, which is the version of go we're now getting in the CI jobs.
We were getting an error: WARN The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar. ERRO [linters_context] exportloopref: This linter is fully inactivated: it will not produce any reports.
There were a couple of deprecation warnings after bumping golangci-lint version: WARN [linters_context] copyloopvar: this linter is disabled because the Go version (1.20) of your project is lower than Go 1.22 WARN [config_reader] The configuration option `run.skip-files` is deprecated, please use `issues.exclude-files`. WARN [config_reader] The configuration option `linters.gci.local-prefixes` is deprecated, please use `prefix()` inside `linters.gci.sections`. WARN [config_reader] The configuration option `linters.staticcheck.go` is deprecated, please use global `run.go`. WARN [config_reader] The configuration option `linters.stylecheck.go` is deprecated, please use global `run.go`.
Linters have picked up a couple of new offenses. Add new exclusion rules.
bfb0689
to
5541d6e
Compare
@mandre: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
OK, this has fixed the failure we saw with pull-cluster-api-provider-openstack-test however I'm not entirely satisfied, we should used a pinned version of go so that we don't run into issues in the future. And there's a chance we have the same problem with the other stable branches. |
I'm not getting why Looking at this job failure, from #2612, we should see lines such as Trying to replicate locally, using the same image that is being used in CI, I'm not having the problem:
|
Trying to debug CI failures in release-0.9 branch.
/hold