-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update golangci-lint to v1.55.2 #9589
Comments
/help |
@killianmuldoon: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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/test-infra repository. |
/assign |
Note v1.55.1 has now been released. |
@adityabhatia are you working on it? If not may I take this over? |
Thanks for the offer @chiukapoor, I will take care of this. |
The PR got merged and this is done right? However, there is already v1.55.2 |
/retitle Update golangci-lint to v1.55.2 @adityabhatia do you want to take care of it again? If not, feel free to unassign, thanks! |
@furkatgofurov7 I can take this |
/close This should be done in #9740 |
@killianmuldoon: Closing this issue. 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/test-infra repository. |
Golangci-lint has a new release - v1.55.0
The release notes are here: https://github.com/golangci/golangci-lint/releases/tag/v1.55.0
After doing an initial test it looks like there's a bunch of new findings - some of them likely spurious and better to ignore. CAPI should update to the new version when possible.
The text was updated successfully, but these errors were encountered: