-
Notifications
You must be signed in to change notification settings - Fork 602
🌱 Bump golangci-lint to v1.62.2 and fix all lint errors #5255
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
Conversation
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ankitasw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This fixes the issue of shadowing the builtins `min`/`max` shadowed by local variables declaration. This has been fixed in newer branches via kubernetes-sigs#5255
/cherry-pick release-2.6 |
@r4f4: only kubernetes-sigs org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually. In response to this:
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. |
/cherry-pick release-2.6 |
@damdo: #5255 failed to apply on top of branch "release-2.6":
In response to this:
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. |
@r4f4 it'll need to be dealt with manually it sounds like |
Manual cherry-pick of kubernetes-sigs#5255
What type of PR is this?
/kind support
/area testing
What this PR does / why we need it:
This updates lots of linters. The new version also gives more consistency between local
make lint
and our GitHub action. For me, the local execution with the old version gave some panics and different results.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Special notes for your reviewer:
Checklist:
Release note: