Skip to content
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

Bump golangci-lint to v1.56.1 #10114

Closed
adityabhatia opened this issue Feb 7, 2024 · 3 comments · Fixed by #10124
Closed

Bump golangci-lint to v1.56.1 #10114

adityabhatia opened this issue Feb 7, 2024 · 3 comments · Fixed by #10124
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@adityabhatia
Copy link
Contributor

adityabhatia commented Feb 7, 2024

Bump golangci-lint to the latest minor release v1.56.0 v1.56.1

The release notes are here: https://github.com/golangci/golangci-lint/releases/tag/v1.56.1

/kind feature

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 7, 2024
@adityabhatia
Copy link
Contributor Author

/assign

@adityabhatia
Copy link
Contributor Author

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 7, 2024
@sbueringer
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 8, 2024
@adityabhatia adityabhatia changed the title Bump golangci-lint to v1.56.0 Bump golangci-lint to v1.56.1 Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants