Closed JohnTitor closed 1 year ago
Should be OK.
Okay, I investigated this and found some blockers. The first is some lints in golangci-lint don't support Go 1.18. In our case, structcheck
and unparam
don't. I think this should be fine as our codebase isn't changed so frequently.
The second is, to get golangci-lint's Go 1.18 support, we have to bump up it to 1.45.0 or higher. This itself isn't a problem but https://github.com/daixiang0/gci/issues/54 is. It reports some false positives, see https://github.com/JohnTitor/krew/runs/6422270074?check_suite_focus=true for example. I checked golangci config and I found we also use goimports. I think it's enough to format/order imports and could remove gci. Is there a reason to have gci here?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Still needs an update from golangci-lint,
/remove-lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Superseded by #801 Well, I thought this is a PR, sorry!
https://github.com/kubernetes-sigs/krew/pull/801 will resolve this but not yet. /remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/close
@ahmetb: Closing this issue.
Is there a policy about bumping up Go version? If not, I'm happy to do it.