-
-
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
gomnd: Versions 1.58.0+ break backward compatibility and do not work with older configs #4767
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Just to clarify, this is what I get with v1.57.0 (golangci-lint has version 1.57.0 built with go1.22.1 from ddc703d on 2024-03-19T23:16:39Z) and the config above:
No warnings. And this is what I get with v1.58.0 (golangci-lint has version 1.58.0 built with go1.22.2 from 28b3813 on 2024-05-03T18:05:38Z)
|
Hello, By default, golangci-lint doesn't provide backward compatibility with linter configuration because we cannot control the linter configuration. The section I will see if we can fix that. |
Doesn't that mean the should have been some warnings? |
The missing warnings have been added in v1.57.2 |
I find a fix: #4768 But following our linter deprecation cycle, I want to inform you that https://golangci-lint.run/product/roadmap/#linter-deprecation-cycle |
Welcome
Description of the problem
Version 1.58.0 has broken BC because gomnd linter was renamed to mnd:
Version of golangci-lint
Configuration
Go environment
Verbose output of running
A minimal reproducible example or link to a public repository
// no actual code is required
Validation
The text was updated successfully, but these errors were encountered: