-
Notifications
You must be signed in to change notification settings - Fork 136
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
chore: go1.23.1 golangci lint 1.6.1 #3940
chore: go1.23.1 golangci lint 1.6.1 #3940
Conversation
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
Signed-off-by: Ramon Petgrave <[email protected]>
0701331
to
1403f7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
The golangci-lint job looks like it should be replaced with golangci/golangci-lint-action
but i'm not very familiar with this (and it's not really related to the chore here) so I'm not strongly suggesting it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to address jku's suggestion in a followup sooner rather than later.
@jku @loosebazooka, A while ago @ianlewis and @laurentsimon and I decided it was better to keep it this way, since we get to verify the golangci-lint binary's hash. Their official action I believe still does not verify the binary of the hash, even if downloading directly from their GitHub repo's releases. We should consider updating the slsa-verifier's implementation to verify the binary, however. |
Summary
Followup to slsa-framework/slsa-verifier#810
fmt.Errorf(err)
tofmt.Error(err)
Testing Process
unit tests continue to pass, as well as the linter
Checklist