-
Notifications
You must be signed in to change notification settings - Fork 553
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
build: use Go 1.22 #4593
build: use Go 1.22 #4593
Conversation
Kubernetes 1.30 packages require Go 1.22 or newer. Signed-off-by: Niels de Vos <ndevos@ibm.com>
golangci-lint reports these: The copy of the 'for' variable "kmsID" can be deleted (Go 1.22+) (copyloopvar) Signed-off-by: Niels de Vos <ndevos@ibm.com>
golangci-lint warns about this: for loop can be changed to use an integer range (Go 1.22+) (intrange) Signed-off-by: Niels de Vos <ndevos@ibm.com>
gosec warns about it like this: G601: Implicit memory aliasing in for loop. (gosec) Signed-off-by: Niels de Vos <ndevos@ibm.com>
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.
Only this linter commit needs a another approach.
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
/test ci/centos/k8s-e2e-external-storage/1.27 |
/test ci/centos/k8s-e2e-external-storage/1.28 |
/test ci/centos/mini-e2e-helm/k8s-1.27 |
/test ci/centos/mini-e2e-helm/k8s-1.28 |
/test ci/centos/mini-e2e/k8s-1.27 |
/test ci/centos/mini-e2e/k8s-1.28 |
/test ci/centos/k8s-e2e-external-storage/1.29 |
/test ci/centos/mini-e2e-helm/k8s-1.29 |
/test ci/centos/mini-e2e/k8s-1.29 |
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/upgrade-tests-rbd |
/retest ci/centos/mini-e2e-helm/k8s-1.28 |
@Mergifyio requeue |
Failed with a mismatch of backend images |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
Kubernetes 1.30 packages require Go 1.22 or newer.
With a new Go version, golangci-lint reports more issues, these are addressed as well.
golangci-lint reports these:
golangci-lint warns about this:
gosec warns about it like this:
Related-to: #4569