You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #625 I've pinned the version to v1.41.0, which I'm using locally, and I had no new linting issues.
My proposal would be to update the linter version every once in a while, fixing all issues at that time. The hard thing is not forgetting to update it 😅 .
The text was updated successfully, but these errors were encountered:
@hslatman totally agree. Let's get up to speed with the latest version (fix all the linter errors and remove go 1.15 testing/linting and pin go1.16 in the go.mod) and then pin golangci-lint in the actions. I regret not doing that before.
Uh oh!
There was an error while loading. Please reload this page.
Golangci-lint not fixed to specific version in CI
Despite the setting in https://github.com/smallstep/certificates/blob/master/.golangci.yml#L79, it seems that golangci-lint is always using the latest version in CI. This results in linting issues being reported not related to new code that's being worked on.
In #625 I've pinned the version to v1.41.0, which I'm using locally, and I had no new linting issues.
My proposal would be to update the linter version every once in a while, fixing all issues at that time. The hard thing is not forgetting to update it 😅 .
The text was updated successfully, but these errors were encountered: