WIP: [NOT READY FOR REVIEW] enforce a floor on libnvjitlink, build wheels with CUDA 13.0.x, test wheels against mix of CTK versions

[jameslamb]

Description

Contributes to rapidsai/build-planning#257

• builds CUDA 13 wheels with the 13.0 CTK
• ensures wheels ship with a runtime dependency of nvidia-nvjitlink>={whatever-minor-version-they-were-built-against}

Contributes to rapidsai/build-planning#256

• updates wheel tests to cover a range of CTK versions (we previously, accidentally, were only testing the latest 12.x and 13.x)

Other changes

• ensures conda packages also take on floors of libnvjitlink>={whatever-version-they-were-built-against}

Notes for Reviewers

How I tested this

This uses wheels from similar PRs from RAPIDS dependencies, at build and test time:

• WIP: build wheels with CUDA 13.0.x, test wheels against mix of CTK versions kvikio#942
• WIP: [NOT READY FOR REVIEW] build wheels with CUDA 13.0.x, test wheels against mix of CTK versions rmm#2270
• WIP: build wheels with CUDA 13.0.x, test wheels against mix of CTK versions ucxx#604

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[jameslamb]

/ok to test

[jameslamb]

/ok to test

[jameslamb]

/ok to test

[jameslamb]

/merge

(edit) Ugh, meant to /ok to test but did this by memory. I've put a DO NOT MERGE label on this so we don't get an unexpected early merge

[jameslamb]

/ok to test

[jameslamb]

😬 I hit GitHub's rate limits

Downloading and decompressing ucxx_wheel_cpp_libucxx_cu12_x86_64 from Run ID into /tmp/tmp.FFhweajGIk

error fetching artifacts: HTTP 403: API rate limit exceeded for installation. If you reach out to GitHub Support for help, please include the request ID B4E0:1E3815:1337C1F:517B113:69AF40CF and timestamp 2026-03-09 21:51:11 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service) (https://api.github.com/repositories/617172783/actions/artifacts?per_page=100&page=322)

(build link)

Look at the limits printed in that job... this repo was pushing it already:

    "core": {
      "limit": 15000,
      "used": 14483,
      "remaining": 517,
      "reset": 1773094676
    },

Seeing that ?page=322 in the message is concerning... nothing in our artifact-fetching should be paging over that many results!

I think the problem is that the run wasn't found. Notice "from Run ID into" (empty space!).

I'll put up a fix for that.

[jameslamb]

Fixing that over here: rapidsai/gha-tools#249

[jameslamb]

/ok to test