Repository navigation
Replies: 2 comments 1 reply
|
Hello, I guess you are asking that because of the eMudhra intermediate CA certificates have been compromised. As we are not relying on CA or certificates, golangci-lint is not affected the CVE fixed inside go1.27.3. If your question is related to a company need, we have a dedicated sponsor tier to ask for a release: |
|
Any planned release for now? Besides linting logic not being affected by the CVE the image still is. |
Uh oh!
There was an error while loading. Please reload this page.
Welcome
How did you install golangci-lint?
Docker
Your feature request related to a problem? Please describe
We are currently using golangci/golangci-lint:v2.15.0. Even though this image was published about a week ago, the binary within was compiled with Go 1.27.0, which includes various bugs and security issues relative to the latest release (1.27.3 at time of this writing).
Describe the solution you'd like
Would it be possible to release a new image tag, compiled with Go 1.27.3?
Also, going forward, would it be possible to release a new image tag whenever a new Go patch version is released?
Describe alternatives you've considered
We could of course compile golangci-lint ourselves and make our own image, but using what's already on DockerHub is much more convenient.
Additional context
No response
🌱 Supporting the Maintainers
All reactions