Revert "Update DLPack to 1.0 (#2354)" - #2366
Merged
rapids-bot[bot] merged 2 commits intoJul 28, 2026
Merged
Conversation
This reverts commit 350a3b0.
|
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. |
trxcllnt
approved these changes
Jul 27, 2026
robertmaynard
approved these changes
Jul 27, 2026
Member
|
cc: @divyegala |
jameslamb
approved these changes
Jul 28, 2026
Contributor
Author
|
/merge |
rapids-bot
Bot
merged commit Jul 28, 2026
c1bcd96
into
NVIDIA:release/26.08
163 of 165 checks passed
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
4 participants
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.
This reverts commit 350a3b0.
This update introduced conflicts with cuDF, which is already in code freeze for 26.08. I have a proposal in rapidsai/build-planning#308 to update to DLPack 1.x, which can occur in 26.10 or later because it is not an ABI breaking change (which was the original reason this targeted 26.08, because 26.08 is allowed to break ABI).