Description
In RAPIDS 26.04, we switched to building CUDA 13 wheels with CUDA Toolkit 13.0: #257
This was done to avoid building against libnvJitLink 13.1, which would have brought in a runtime requirement of nvidia-nvjitlink>=13.1, which would have made RAPIDS wheels uninstallable against any available torch wheels (for CUDA 13).
Eventually we will want to switch back to building RAPIDS wheels against the latest available CTK. This tracks that work.
Benefits of this work
- take advantage of bugfixes, performance improvements, and new features in new CTKs
Acceptance Criteria
RAPIDS wheels:
- are built against the latest CTK at the time this is picked up
- all have appropriate runtime dependencies (e.g.
nvidia-nvjitlink floor updated)
- every project with
torch wheel tests uses CUDA torch wheels for CUDA 12 and 13 (ideally without needing pip install --no-deps to piece together the environment)
Approach
Notes
N/A
Description
In RAPIDS 26.04, we switched to building CUDA 13 wheels with CUDA Toolkit 13.0: #257
This was done to avoid building against libnvJitLink 13.1, which would have brought in a runtime requirement of
nvidia-nvjitlink>=13.1, which would have made RAPIDS wheels uninstallable against any availabletorchwheels (for CUDA 13).Eventually we will want to switch back to building RAPIDS wheels against the latest available CTK. This tracks that work.
Benefits of this work
Acceptance Criteria
RAPIDS wheels:
nvidia-nvjitlinkfloor updated)torchwheel tests uses CUDAtorchwheels for CUDA 12 and 13 (ideally without needingpip install --no-depsto piece together the environment)Approach
shared-workflowschanges ([DO NOT MERGE] wheels-build: use newest CTK (13.3.0) for wheel builds shared-workflows#590)@main)@main/@release/YY.MMofshared-workflowsagainci-imgschangesci-wheelimages ([DO NOT MERGE] ci-wheel: drop CUDA 13.0 images ci-imgs#440)Notes
N/A