Update golangci-lint to 2.10.1 and related changes - #5678
Conversation
|
I also added Unfotunately golangci-lint flip-flops between whether or not some //nolint: are needed before and after adding nromalize ... and especially after some of the changes it does. I do not have idea why that happens. |
|
It seems that the cache for golangci-lint is giving a lot of nolintlint problems - I got the CI failing and deleteing golangci-lint cache fixed the failure |
Apart from fixing some lint issues I also removed gosec for test files as there are just too many false positives. This did require removing some nolints from there but it still seems like less actual changes. Also not certain how useful gosec is in test files.
Most of this was done with `golangci-lint run --fix` and then fixing that (a couple of bad changes). Somehow this required some of the `//nolint:...` to be readded that were removed in the previous one.
a7f5a23 to
1df6ed3
Compare
| import ( | ||
| "errors" | ||
| "fmt" | ||
| maps0 "maps" |
There was a problem hiding this comment.
This looks a bit weird, and I guess it would be better to rename the variable, but of course it's non-blocking as it's correct.
There was a problem hiding this comment.
I do agree with you, but I would prefer to fix this across all the mapping files - it is just that only here we do copy a map ...
There was a problem hiding this comment.
Yeah, yeah, sure! No need to do it in this PR, let's get it merged instead! 🚀 Thanks!
What?
Update golangci-lint to latest version.
Apart from fixing some lint issues I also removed gosec for test files as there are just too many false positives.
This did require removing some nolints from there but it still seems like less actual changes.
Also not certain how useful gosec is in test files.
Why?
Apart from keeping on top of the new updates and improvements (usually around less false possitives) it allows us to update go 1.26 which isn't supported until 2.10.
Checklist
make check) and all pass.Checklist: Documentation (only for k6 maintainers and if relevant)
Please do not merge this PR until the following items are filled out.
Related PR(s)/Issue(s)