Skip to content

Forward-merge release/26.04 into main#5465

Open
rapids-bot[bot] wants to merge 1 commit intomainfrom
release/26.04
Open

Forward-merge release/26.04 into main#5465
rapids-bot[bot] wants to merge 1 commit intomainfrom
release/26.04

Conversation

@rapids-bot
Copy link

@rapids-bot rapids-bot bot commented Mar 13, 2026

Forward-merge triggered by push to release/26.04 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

…ncies (#5453)

Contributes to rapidsai/build-planning#257

* ensures that when `torch` is installed in wheels CI, it's always a CUDA variant
* removes unused test dependencies `ogb`, `pydantic`, `torchdata`, and `torchmetrics`
  - *I suspect these are left over from before GNN packages moved out to https://github.com/rapidsai/cugraph-gnn*

## Notes for Reviewers

### How does this help with testing against a mix of CTKs?

`torch` CUDA wheels tightly pin to `nvidia-{thing}` wheels and soon, `cuda-toolkit` (see rapidsai/build-planning#255).

Forcing the use of CUDA `torch` wheels ensures we'll catch dependency conflicts in CI. Without this, `pip` could silently fall back to CPU-only `torch` from pypi.org.

### How I tested this

This PR uses some patterns I've tested elsewhere too:

* rapidsai/rmm#2270 (comment)
* rapidsai/cugraph-gnn#425

I also tested a commit here with both the PR and nightly test matrices, to be sure we covered everything: https://github.com/rapidsai/cugraph/actions/runs/23062364778/job/66996357196?pr=5453

Authors:
  - James Lamb (https://github.com/jameslamb)

Approvers:
  - Alex Barghi (https://github.com/alexbarghi-nv)
  - Gil Forsyth (https://github.com/gforsyth)

URL: #5453
@rapids-bot rapids-bot bot requested review from a team as code owners March 13, 2026 21:35
@rapids-bot rapids-bot bot requested a review from bdice March 13, 2026 21:35
@rapids-bot
Copy link
Author

rapids-bot bot commented Mar 13, 2026

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

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.

1 participant