New Release? #6406
-
|
The GoSec release 1.23.0 used in the latest release of golangci-lint introduced multiple false positives, there have been fixes for them (two I reported personally) and 57 commits since the latest release securego/gosec@v2.23.0...v2.24.7. I was hoping we could get a new golangci-lint release this week to address these issues. ❤️ thank you ldez for maintaining the project. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hello, at least, I need to handle the change behind #6404, before creating a release.
But, the migration path is not documented: maybe there is nothing to change but the action name, or not. My plan was also to integrate https://github.com/ldez/usenew but I still need to work on it, so maybe I will postpone this element for now. |
Beta Was this translation helpful? Give feedback.
-
|
Totally understand that you want to crush the tech debt before creating a new release. We can maybe compile from main for now until one is created. Thank you for considering it. |
Beta Was this translation helpful? Give feedback.
Hello, at least, I need to handle the change behind #6404, before creating a release.
actions/attest-build-provenancehas been "replaced" withactions/attest.We can keep
actions/attest-build-provenance, but I'm sure that will lead to problems in the future, so I prefer to migrate as soon as possible.But, the migration path is not documented: maybe there is nothing to change but the action name, or not.
For now, I don't know, but I will handle this topic today.
My plan was also to integrate https://github.com/ldez/usenew but I still need to work on it, so maybe I will postpone this element for now.