Update to 26.08#1259
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (19)
✅ Files skipped from review due to trivial changes (18)
📝 WalkthroughWalkthroughThis PR migrates the project version from 26.06 to 26.08 across all configuration, dependency, CI/CD, and documentation artifacts. Core version constants, CI workflows, the centralized dependency matrix, generated conda environments, Python packages, and all associated metadata and documentation are uniformly updated. ChangesVersion 26.06 to 26.08 migration
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/build.yaml:
- Line 315: Replace the invalid Docker image tag "python:26.08-slim" used for
the build-summary container with a valid Python base image tag (for example
"python:3.11-slim" or another supported 3.x slim tag) so the container can be
pulled successfully; update the image value in the workflow definition where
"python:26.08-slim" appears.
In @.github/workflows/nightly-summary.yaml:
- Line 63: The workflow's container image value is invalid
("python:26.08-slim"); update the image field for the nightly-summary job to a
valid Python base image (for example change image: python:26.08-slim to image:
python:3.11-slim or another existing tag) so the GitHub Actions runner can pull
the image successfully; locate the image: line in the nightly-summary job
definition and replace the tag accordingly.
In `@python/libcuopt/pyproject.toml`:
- Line 34: The declared dependency "librmm==26.8.*,>=0.0.0a0" in pyproject.toml
is invalid because that release does not exist; update the constraint to a real
release (for example replace "librmm==26.8.*,>=0.0.0a0" with a valid version
constraint such as "librmm==26.4.*" or a specific existing tag like
"librmm==26.04.00") or, if this is intentionally a pre-release, document and
wire up the correct pre-release source/repository before merging; make the
change for all occurrences of that exact string in pyproject.toml (e.g., the
same dependency entry referenced elsewhere).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 2ed0f56c-0bc8-4ea3-b9dd-2f4bc5cca525
📒 Files selected for processing (17)
.github/workflows/build.yaml.github/workflows/build_test_publish_images.yaml.github/workflows/nightly-summary.yaml.github/workflows/pr.yaml.github/workflows/test.yamlRAPIDS_BRANCHVERSIONconda/environments/all_cuda-129_arch-aarch64.yamlconda/environments/all_cuda-129_arch-x86_64.yamlconda/environments/all_cuda-132_arch-aarch64.yamlconda/environments/all_cuda-132_arch-x86_64.yamldependencies.yamldocs/cuopt/source/versions1.jsonpython/cuopt/pyproject.tomlpython/cuopt_self_hosted/pyproject.tomlpython/cuopt_server/pyproject.tomlpython/libcuopt/pyproject.toml
| dependencies = [ | ||
| "cuda-toolkit[cublas,cudart,curand,cusolver,cusparse,nvtx]==13.*", | ||
| "librmm==26.6.*,>=0.0.0a0", | ||
| "librmm==26.8.*,>=0.0.0a0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check if librmm 26.8.* is available in conda repositories
# Check conda package availability for librmm 26.8.*
echo "Checking conda package availability for librmm 26.8.*..."
conda search "librmm=26.8.*" -c rapidsai-nightly -c rapidsai -c conda-forge --json 2>/dev/null | jq -r 'keys[]' | head -n 5 || echo "librmm 26.8.* not found in conda repositories"
# Check PyPI for librmm package (if applicable)
echo -e "\nChecking PyPI for librmm 26.8.*..."
curl -s "https://pypi.org/pypi/librmm/json" 2>/dev/null | jq -r '.releases | keys[]' | grep "^26\.8\." | head -n 5 || echo "librmm 26.8.* not found on PyPI"Repository: NVIDIA/cuopt
Length of output: 217
🌐 Web query:
librmm 26.8 release notes breaking changes RAPIDS
💡 Result:
I couldn’t find any RAPIDS/RMM “librmm 26.8” (v26.08) release notes or changelog page yet. The public RMM releases I can locate for 2026 show v26.02.00 and v26.04.00 as the latest tagged versions, and the docs page I find for librmm is for “stable (26.02)” and “nightly (26.04)” rather than 26.08.[1][2][3][4] What I can confirm about breaking changes (closest available releases): 1) v26.02.00 breaking changes include: - Removing host memory resources.[1] - Removing the legacy memory resource interface in favor of the CCCL interface.[1] - Removing default host alignment.[1] - CCCL 3.2 compatibility updates (resource ref compatibility).[1] - Defaulting to static linking of libcudart.[1] - Storing any_resource in device_buffer and device_uvector.[1] 2) v26.04.00 breaking changes include: - Remove zero-value special casing in set_element_async to preserve IEEE 754 -0.0.[3] If you meant a different version/tag (for example v26.08.00, or RAPIDS “26.08” as part of a larger RAPIDS release train), tell me the exact tag/commit or where you saw “26.8”, and I’ll re-search specifically for that release’s changelog page.
Citations:
- 1: https://github.com/rapidsai/rmm/releases/tag/v26.02.00
- 2: https://docs.rapids.ai/api/librmm/26.04/index.html
- 3: https://github.com/rapidsai/rmm/releases/tag/v26.04.00
- 4: https://docs.rapids.ai/api/librmm/stable/
Fix unavailable librmm dependency version.
The librmm version 26.8.* specified in lines 34 and 79 does not exist in any public repository (conda, PyPI, or RAPIDS releases). The latest available librmm releases are v26.02.00 and v26.04.00. Either update the version constraints to an available release (e.g., librmm==26.4.*) or confirm this is a pre-release version with proper access and documentation before merging.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@python/libcuopt/pyproject.toml` at line 34, The declared dependency
"librmm==26.8.*,>=0.0.0a0" in pyproject.toml is invalid because that release
does not exist; update the constraint to a real release (for example replace
"librmm==26.8.*,>=0.0.0a0" with a valid version constraint such as
"librmm==26.4.*" or a specific existing tag like "librmm==26.04.00") or, if this
is intentionally a pre-release, document and wire up the correct pre-release
source/repository before merging; make the change for all occurrences of that
exact string in pyproject.toml (e.g., the same dependency entry referenced
elsewhere).
rgsl888prabhu
left a comment
rgsl888prabhu
left a comment
There was a problem hiding this comment.
Rest looks good, have just one comment
| runs-on: linux-amd64-cpu4 | ||
| container: | ||
| image: python:26.08-slim | ||
| image: python:3.14-slim |
There was a problem hiding this comment.
Ahh, you fixed in the next commit
2 participants
This PR updates the repository to version 26.08.
This is part of the 26.06 release burndown process.