Merge release/26.02 into main#2216
Merged
jameslamb merged 2 commits intorapidsai:mainfrom Jan 15, 2026
Merged
Conversation
…rapidsai#2214) rapidsai#2212 was into `main` after `main` had already been updated to RAPIDS 26.04. This change is intended for RAPIDS 26.02, so this PR backports it to the `release/26.02` branch. ## Notes for Reviewers ### How this should be merged I think normal squash and merge should be fine? The commit SHA is different because of the direction of the `cherry-pick` anyway. ### How I made this branch ```shell git checkout main git pull upstream main git fetch upstream release/26.02 git checkout release/26.02 git checkout -b pip-changes git cherry-pick f380eff ``` Co-authored-by: Mike McCarty <mmccarty@nvidia.com>
jameslamb
added
non-breaking
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Closes #2215
Fixes forward-merger conflicts, following the process at https://docs.rapids.ai/maintainers/forward-merge
Checklist