Skip to content

Upgrade to CUDA 13.0#45

Closed
regro-cf-autotick-bot wants to merge 2 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:rebuild-cuda130-0-1_h7891d7
Closed

Upgrade to CUDA 13.0#45
regro-cf-autotick-bot wants to merge 2 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:rebuild-cuda130-0-1_h7891d7

Conversation

@regro-cf-autotick-bot
Copy link
Copy Markdown
Contributor

This PR has been triggered in an effort to update cuda130.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.


Here are some more details about this specific migrator:

CUDA 13.0 requires architecture sm_75 or higher, and renamed sm_101 to
sm_110. To build for these, maintainers will need to modify their existing list of
specified architectures (e.g. CMAKE_CUDA_ARCHITECTURES, TORCH_CUDA_ARCH_LIST, etc.)
for their package.

Since CUDA 12.8, the conda-forge nvcc package now sets CUDAARCHS and
in its activation script to a string containing all
of the supported real architectures plus the virtual architecture of the
latest. Recipes for packages who use these variables to control their build
but do not want to build for all supported architectures will need to override
these variables in their build script.

ref: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#new-features

[[!IMPORTANT]]
Remember to update any CUDA 11/12 specific selector syntax in the recipe to include
CUDA 13. For example # [(cuda_compiler_version or "None").startswith("12")]
might be replaced with # [cuda_compiler_version != "None"].


If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/21493727976 - please use this URL for debugging.

CUDA 13.0 requires architecture `sm_75` or higher, and renamed `sm_101` to
`sm_110`. To build for these, maintainers will need to modify their existing list of
specified architectures (e.g. `CMAKE_CUDA_ARCHITECTURES`, `TORCH_CUDA_ARCH_LIST`, etc.)
for their package.

Since CUDA 12.8, the conda-forge nvcc package now sets `CUDAARCHS` and
in its activation script to a string containing all
of the supported real architectures plus the virtual architecture of the
latest. Recipes for packages who use these variables to control their build
but do not want to build for all supported architectures will need to override
these variables in their build script.

ref: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#new-features

> [[!IMPORTANT]]
> Remember to update any CUDA 11/12 specific selector syntax in the recipe to include
> CUDA 13. For example `# [(cuda_compiler_version or "None").startswith("12")]`
> might be replaced with `# [cuda_compiler_version != "None"]`.
@conda-forge-admin
Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@weiji14 weiji14 marked this pull request as draft January 29, 2026 22:37
@carterbox
Copy link
Copy Markdown
Member

#44

@carterbox carterbox closed this Feb 2, 2026
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.

3 participants