Skip to content

Conversation

@loafoe
Copy link

@loafoe loafoe commented May 27, 2025

Overview

Upgrade golangci to 2.4.0 and fix the newly found issues.

What this PR does / why we need it

Use a more recent linter

Special notes for your reviewer

@loafoe loafoe force-pushed the chore/golangci-migrate branch from 9152b94 to 07fa96b Compare May 27, 2025 11:26
@loafoe loafoe changed the title chore: Upgrade golangci to 2.1.6 chore(lint): Upgrade golangci to 2.1.6 May 27, 2025
@loafoe
Copy link
Author

loafoe commented Jun 21, 2025

@sagikazarmark possible to review this one?

Copy link
Contributor

@cardoe cardoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to at least trigger the CI on this one.

@sagikazarmark
Copy link
Member

@loafoe thanks for the PR.

Would you mind rebasing and applying your fixes to the latest master? We've updated the linter with the Go version.

@loafoe loafoe force-pushed the chore/golangci-migrate branch from 07fa96b to 9d18274 Compare August 18, 2025 13:34
@loafoe loafoe changed the title chore(lint): Upgrade golangci to 2.1.6 chore(lint): Upgrade golangci to 2.4.0 Aug 18, 2025
@loafoe
Copy link
Author

loafoe commented Aug 18, 2025

@sagikazarmark rebased to master 👍🏻

@loafoe loafoe requested a review from cardoe August 18, 2025 15:43
@sagikazarmark sagikazarmark added the release-note/ignore Ignore this change when generating release notes label Aug 19, 2025
@loafoe loafoe force-pushed the chore/golangci-migrate branch from 9d18274 to fdc2371 Compare October 6, 2025 12:52
@loafoe
Copy link
Author

loafoe commented Oct 6, 2025

@sagikazarmark @cardoe FYI rebased to master

@loafoe loafoe requested a review from cardoe October 6, 2025 12:56
@cardoe
Copy link
Contributor

cardoe commented Oct 11, 2025

@loafoe it failed tests

Signed-off-by: Andy Lo-A-Foe <[email protected]>
@loafoe loafoe force-pushed the chore/golangci-migrate branch from fdc2371 to dea90b8 Compare January 7, 2026 12:11
@loafoe
Copy link
Author

loafoe commented Jan 7, 2026

@cardoe possible to retrigger the tests so I can verify tests are fixed?

@sagikazarmark
Copy link
Member

I triggered the tests, but they are still failing. Looks like something related to the Kubernetes storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-note/ignore Ignore this change when generating release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants