Closed ItalyPaleAle closed 1 year ago
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.
Hello,
You have checked the following box:
[x] Yes, I've tried with the standalone linter if available (e.g., gocritic, go vet, etc.). (https://golangci-lint.run/usage/linters/)
unused
is related to staticcheck
, can you give me the output of the run of the standalone binary of staticcheck
? (golangci-lint v1.51.1 uses honnef.co/go/tools@v0.4.0
)
https://github.com/golangci/golangci-lint/blob/v1.51.1/go.mod#L115
I think the problem is already fixed by https://github.com/golangci/golangci-lint/pull/3591 but you have to check.
Thanks for the quick response :)
I checked that box because I tried installing the unused
linter directly and I couldn't get it to work, so I figured it fell under the "if [not] available"
I can confirm that the issue is reproducible with staticheck v0.4.0, but it's fixed with the latest
version of staticheck.
So looks like #3591 does fix that. Thanks!
Welcome
Description of the problem
After updating to 1.51.1 (due to Go 1.20), we are getting linter failures due to the
unused
linter reporting issues form 3rd-party dependencies:Although these issues are valid, we cannot act on them as they're external dependencies
Version of golangci-lint
Configuration file
Go environment
Verbose output of running
Code example or link to a public repository