-
Notifications
You must be signed in to change notification settings - Fork 49
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
fix(deps): update go to 1.21 #738
fix(deps): update go to 1.21 #738
Conversation
Signed-off-by: Mend Renovate <bot@renovateapp.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>
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>
This reverts commit e8befa2. Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
This reverts commit 0bc2c70. Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
This reverts commit 8c346b8. Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
4981e1e
to
a24f036
Compare
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>
This reverts commit f468545. Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
7dda203
to
f2d691f
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.
LGTM overall. There may be a rebase issue to fix before merging
Enabling auto-merge |
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Head branch was pushed to by a user without write access
# TODO(2680): re-enable go-version-file | ||
# go-version-file: "go.mod" | ||
go-version: '1.20' | ||
go-version-file: "go.mod" |
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.
What was the issue with using go-version-file
before? I guess we fixed it in 1.9.0
.
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.
I'm not sure what the issue was before, but using go-version-file
instead of go-version
lets use specify which version to use in only one place.
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.
Yeah, I remember we fixed an issue with it and maybe that was in 1.9.0
?
slsa-framework/slsa-github-generator#2661
But it looks like we haven't released that fix yet.
slsa-framework/slsa-github-generator@00c744f
Signed-off-by: Ramon Petgrave <ramon.petgrave64@gmail.com>
Fixing the existing PR #498 to also change the github actions to use the go 1.21 sourced directly from
go.mod
.Also fixing some more lint checks about repeated strings