-
Notifications
You must be signed in to change notification settings - Fork 251
chore: Update the go version to fix vulnerability #4284
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
Conversation
michaelkedar
left a comment
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.
do we need to / should we be updating the go versions in the Dockerfiles also?
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.
was this intentional?
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.
+1
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.
nope
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.
+1
ad76e04 to
78b0b77
Compare
|
Hmm interestingly most golang ones are on go 1.25. I'll update everything to 1.25.3 to keep things consistent |
OSV-Scanner is reporting new vulns for go 1.24.6, so bumping everything up to 1.25.3. Hopefully in the future renovatebot can do this for us.