Skip to content
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

Merged
merged 5 commits into from
Oct 14, 2024

Conversation

ramonpetgrave64
Copy link
Collaborator

Summary

Followup to slsa-framework/slsa-verifier#810

  • upgrades to go 1.23.1 and golangci-lint 1.6.1
  • makes necessary changes for the linter
    • as of go 1.22, no need to make a copy of the loop variable
    • change non-string use of fmt.Errorf(err) to fmt.Error(err)

Testing Process

unit tests continue to pass, as well as the linter

Checklist

  • Review the contributing guidelines
  • Add a reference to related issues in the PR description.
  • Update documentation if applicable.
  • Add unit tests if applicable.
  • Add changes to the CHANGELOG if applicable.

Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
@ramonpetgrave64 ramonpetgrave64 force-pushed the ramonpetgrave64-go1.23.1-golangci-lint-1.6.1 branch from 0701331 to 1403f7c Compare October 11, 2024 09:30
@ramonpetgrave64 ramonpetgrave64 marked this pull request as ready for review October 11, 2024 09:34
@ramonpetgrave64
Copy link
Collaborator Author

@jku @loosebazooka

Copy link

@jku jku left a 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.

Copy link
Contributor

@loosebazooka loosebazooka left a 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.

@ramonpetgrave64
Copy link
Collaborator Author

ramonpetgrave64 commented Oct 14, 2024

@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.

@ramonpetgrave64 ramonpetgrave64 merged commit edb0d82 into main Oct 14, 2024
94 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants