Skip to content

Conversation

tenzen-y
Copy link
Contributor

@tenzen-y tenzen-y commented Jun 26, 2025

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

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
Copy link
Contributor

@mbobrovskyi mbobrovskyi Jun 26, 2025

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:

golang: 1.24.2

FROM golang:1.24.2-bullseye AS builder

FROM golang:1.24.2-bullseye AS builder

FROM golang:1.24.2-bullseye AS builder

FROM golang:1.24.2-bullseye AS generator

go install golang.org/dl/go1.24.2@latest
go1.24.2 download
export GOROOT=$(go1.24.2 env GOROOT)

Copy link
Contributor Author

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.

Copy link
Contributor Author

@tenzen-y tenzen-y Jun 26, 2025

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

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?

Copy link
Contributor Author

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.

@tenzen-y
Copy link
Contributor Author

tenzen-y commented Jul 3, 2025

@kevin85421 I replaced all Go versions with v1.24.0.
PTAL, thanks.

@kevin85421
Copy link
Member

@tenzen-y thanks! Please ping me when all CI tests pass. Thank you!

Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
@tenzen-y
Copy link
Contributor Author

tenzen-y commented Jul 3, 2025

I accidentally replaced the ENVTEST_K8S_VERSION even though that is not Go version.
So, I reverted the change.

@tenzen-y
Copy link
Contributor Author

tenzen-y commented Jul 3, 2025

@kevin85421 Sorry for the bother. Could you approve actions CI?

@kevin85421
Copy link
Member

@kevin85421 Sorry for the bother. Could you approve actions CI?

Approved

@tenzen-y
Copy link
Contributor Author

tenzen-y commented Jul 3, 2025

@kevin85421 Sorry for the bother. Could you approve actions CI?

Approved

@kevin85421 Thank you.
All CIs are succeeded.

@tenzen-y
Copy link
Contributor Author

tenzen-y commented Jul 3, 2025

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?

@kevin85421
Copy link
Member

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 kevin85421 merged commit 9be8abd into ray-project:master Jul 3, 2025
25 checks passed
@tenzen-y
Copy link
Contributor Author

tenzen-y commented Jul 4, 2025

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?

tenzen-y added a commit to tenzen-y/kuberay that referenced this pull request Jul 4, 2025
@tenzen-y tenzen-y deleted the use-go-1240 branch July 4, 2025 04:41
@mimowo
Copy link

mimowo commented Jul 4, 2025

Thank you @tenzen-y for driving it.

@mimowo, Do you have any timeline for upgrading the KubeRay version in the Kueue repository?

I would like to upgrade it before the next minor release of Kueue which is planned for mid July.

@kevin85421 kevin85421 mentioned this pull request Jul 5, 2025
2 tasks
DW-Han pushed a commit to DW-Han/kuberay that referenced this pull request Jul 30, 2025
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.

Avoid requiring specific Go patch version in go module
4 participants