[Docs][KubeRay] Update all KubeRay version references to 1.6.0#61865
Conversation
Future-Outlier
force-pushed
the
kuberay-version-1.6.0
branch
from
d709687 to
bda9262
Compare
Signed-off-by: Future-Outlier <eric901201@gmail.com>
Future-Outlier
force-pushed
the
kuberay-version-1.6.0
branch
from
bda9262 to
50d603c
Compare
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request correctly updates most KubeRay version references from v1.5.1 to v1.6.0 across the documentation and some scripts. The changes are largely mechanical but have been executed well.
I've pointed out one inconsistency between the PR description and the changes in doc/source/cluster/kubernetes/getting-started/rayjob-quick-start.md.
Additionally, I noticed a potential missed update in doc/source/cluster/kubernetes/examples/argocd.md. In the "Alternative: Deploy Everything in One File" section, targetRevision for the ray-cluster chart is still set to "1.4.1". Since this line was not part of the diff, I couldn't leave a direct comment, but it might be worth checking if this should also be updated to 1.6.0 for consistency.
Overall, a good set of updates to align with the new release.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d709687b5d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Signed-off-by: Future-Outlier <eric901201@gmail.com>
Signed-off-by: Future-Outlier <eric901201@gmail.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f9e9cb8dcc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
ray-gardener
Bot
added
docs
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a8d9a571de
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
themavik
left a comment
themavik
left a comment
There was a problem hiding this comment.
The decision log for edge cases is thorough — keeping historical facts (e.g., label-based-scheduling v1.5.1) and feature-stage evolution (alpha in v1.5.1, beta in v1.6.0) separate from current version pointers is the right call. The observability.md 1.2.2 skip is a sensible conservative choice.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c901bf645
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Future-Outlier
force-pushed
the
kuberay-version-1.6.0
branch
from
1ff209b to
75eee90
Compare
Signed-off-by: Future-Outlier <eric901201@gmail.com>
…roject#61865) the prompt I used with claude Opus 4.6 (1M context), max mode: ``` Update all KubeRay version references to 1.6.0 in the ray-project/ray documentation. For example, the docs may contain: helm install kuberay-operator --version 1.5.0 helm install kuberay-operator --version 1.6.0 Reference these previous version bump PRs for the pattern of which files and version strings to update: - ray-project#58885 - ray-project#58452 - ray-project#53884 Update everything related to the KubeRay operator version to 1.6.0. If unsure about any specific reference, ask before changing. Check every file. ``` Decision log for edge cases ```┌─────┬──────────────────────────────────────┬────────────────────────────────────────────────────┬──────────────────────┬──────────────────────────────────────────────┐ │ # │ File │ Question │ Decision │ Principle │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ 1 │ observability.md │ --version 1.2.2 was never updated by previous PRs. │ Keep as-is │ Needs more careful review; skipped by all 3 │ │ │ │ Update to 1.6.0? │ │ previous version bump PRs for a reason. │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ │ │ Out of scope — this is in the Serve docs, │ │ 2 │ serve/production-guide/kubernetes.md │ kuberay/blob/v1.0.0 reference. Update? │ Don't change │ not the KubeRay cluster docs. Previous PRs │ │ │ │ │ │ never touched it. │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ deletionStrategy (Optional, alpha in v1.5.1) — │ Write both: alpha in │ Document feature stage evolution across │ │ 3 │ rayjob-quick-start.md │ update version? │ v1.5.1, beta in │ versions. │ │ │ │ │ v1.6.0 │ │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ "available in Ray 2.51.0 and KubeRay v1.5.1" — │ │ Historical fact about when the feature │ │ 4 │ label-based-scheduling.md │ update to v1.6.0? │ Keep v1.5.1 │ became available. Changing it would be │ │ │ │ │ │ inaccurate. │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ "minimum version for this guide is v1.5.1" and │ │ Historical fact about feature introduction │ │ 5 │ rayservice-incremental-upgrade.md │ "implemented with alpha support in KubeRay v1.5.1" │ Keep v1.5.1 │ and minimum version requirement. │ │ │ │ — update? │ │ │ └─────┴──────────────────────────────────────┴────────────────────────────────────────────────────┴──────────────────────┴──────────────────────────────────────────────┘ ``` General principles applied - Current version pointers (URLs, helm commands, install steps) → Update to 1.6.0 - Historical facts (feature introduction version, minimum version requirements) → Keep original version - Feature stage changes (alpha → beta) → Write both versions to document evolution - Out-of-scope references (Serve docs, unrelated sections) → Don't change --------- Signed-off-by: Future-Outlier <eric901201@gmail.com>
…roject#61865) the prompt I used with claude Opus 4.6 (1M context), max mode: ``` Update all KubeRay version references to 1.6.0 in the ray-project/ray documentation. For example, the docs may contain: helm install kuberay-operator --version 1.5.0 helm install kuberay-operator --version 1.6.0 Reference these previous version bump PRs for the pattern of which files and version strings to update: - ray-project#58885 - ray-project#58452 - ray-project#53884 Update everything related to the KubeRay operator version to 1.6.0. If unsure about any specific reference, ask before changing. Check every file. ``` Decision log for edge cases ```┌─────┬──────────────────────────────────────┬────────────────────────────────────────────────────┬──────────────────────┬──────────────────────────────────────────────┐ │ # │ File │ Question │ Decision │ Principle │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ 1 │ observability.md │ --version 1.2.2 was never updated by previous PRs. │ Keep as-is │ Needs more careful review; skipped by all 3 │ │ │ │ Update to 1.6.0? │ │ previous version bump PRs for a reason. │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ │ │ Out of scope — this is in the Serve docs, │ │ 2 │ serve/production-guide/kubernetes.md │ kuberay/blob/v1.0.0 reference. Update? │ Don't change │ not the KubeRay cluster docs. Previous PRs │ │ │ │ │ │ never touched it. │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ deletionStrategy (Optional, alpha in v1.5.1) — │ Write both: alpha in │ Document feature stage evolution across │ │ 3 │ rayjob-quick-start.md │ update version? │ v1.5.1, beta in │ versions. │ │ │ │ │ v1.6.0 │ │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ "available in Ray 2.51.0 and KubeRay v1.5.1" — │ │ Historical fact about when the feature │ │ 4 │ label-based-scheduling.md │ update to v1.6.0? │ Keep v1.5.1 │ became available. Changing it would be │ │ │ │ │ │ inaccurate. │ ├─────┼──────────────────────────────────────┼────────────────────────────────────────────────────┼──────────────────────┼──────────────────────────────────────────────┤ │ │ │ "minimum version for this guide is v1.5.1" and │ │ Historical fact about feature introduction │ │ 5 │ rayservice-incremental-upgrade.md │ "implemented with alpha support in KubeRay v1.5.1" │ Keep v1.5.1 │ and minimum version requirement. │ │ │ │ — update? │ │ │ └─────┴──────────────────────────────────────┴────────────────────────────────────────────────────┴──────────────────────┴──────────────────────────────────────────────┘ ``` General principles applied - Current version pointers (URLs, helm commands, install steps) → Update to 1.6.0 - Historical facts (feature introduction version, minimum version requirements) → Keep original version - Feature stage changes (alpha → beta) → Write both versions to document evolution - Out-of-scope references (Serve docs, unrelated sections) → Don't change --------- Signed-off-by: Future-Outlier <eric901201@gmail.com>
4 participants
the prompt I used with claude Opus 4.6 (1M context), max mode:
Decision log for edge cases
General principles applied