-
|
While using golangci-lint in CI systems, it feels kinda weird that on every minor go upgrade your CI pipelines will fail because of
I just try to understand why it is that special for go/golangci-lint because I never had this case with any other programming language that my CI pipeline is stuck until my linters got upgraded to support new language versions. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
golangci-lint depends on the language types, the language types are inside Go itself. go "minor" versions are containing new types, types changes (ex: new methods), etc. Go provides compatibility to the previous versions but not with the next versions. This is like if you are trying to compile a project that define a min language requirement to the version X but you are trying to compile with the version X-1, it will not work. You will find the same kind of problems with Typescript and ESLint. |
Beta Was this translation helpful? Give feedback.
golangci-lint depends on the language types, the language types are inside Go itself.
go "minor" versions are containing new types, types changes (ex: new methods), etc.
Go provides compatibility to the previous versions but not with the next versions.
As golangci-lint depends on it, so it has to follow it.
This is like if you are trying to compile a project that define a min language requirement to the version X but you are trying to compile with the version X-1, it will not work.
You will find the same kind of problems with Typescript and ESLint.