-
Notifications
You must be signed in to change notification settings - Fork 608
Use Go 1.24.0 in go module #3835
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
Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
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.
Please also update other places:
kuberay/.pre-commit-config.yaml
Line 6 in c4c01ce
golang: 1.24.2 |
kuberay/ray-operator/Dockerfile
Line 2 in c4c01ce
FROM golang:1.24.2-bullseye AS builder |
Line 2 in c4c01ce
FROM golang:1.24.2-bullseye AS builder |
kuberay/experimental/Dockerfile
Line 2 in c4c01ce
FROM golang:1.24.2-bullseye AS builder |
Line 2 in c4c01ce
FROM golang:1.24.2-bullseye AS generator |
kuberay/ray-operator/DEVELOPMENT.md
Lines 27 to 29 in c4c01ce
go install golang.org/dl/go1.24.2@latest | |
go1.24.2 download | |
export GOROOT=$(go1.24.2 env GOROOT) |
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.
Good point.
However, I think we might want to keep Go version in Dockerfile.
I can up the decision to KubeRay maintainers. @andrewsykim @kevin85421
Anyway, pre-commit-config and DEVELOPMENT.md should be updated.
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.
As I revisit for pre-commit-config and DEVELOPMENT.md, those can also still point to the 1.24.2 since 1.24.0
in go.mod indicates greater than 1.24.0 should be compatible.
Anyway, I want to hear the KubeRay maintainer's opinion.
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.
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.
Sorry for the late response—I just finished the release process this week. It's better to keep the Go version consistent across the entire repo. How about updating the Dockerfile's Go version to 1.24.0 as well?
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.
Thank you for checking that!
Sure, we can replace all with 1.24.0.
@kevin85421 I replaced all Go versions with v1.24.0. |
@tenzen-y thanks! Please ping me when all CI tests pass. Thank you! |
Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
I accidentally replaced the |
@kevin85421 Sorry for the bother. Could you approve actions CI? |
Approved |
@kevin85421 Thank you. |
Additionally, I hope to deliver this change to the next kuberay patch version so that we can avoid Go patch version delivering. Could we cherry-pick to the release branch? |
Sure, do you have a timeline in mind? |
@kevin85421 I do not have a specific timeline, but this is a blocker for kubernetes-sigs/kueue#5722. @mimowo, Do you have any timeline for upgrading the KubeRay version in the Kueue repository? |
Why are these changes needed?
As I described in the related issue, this patch version will be delivered to child and grand child projets.
I would like to avoid such situations.
Related issue number
Closes #3834
Checks