Merged
Conversation
bdice
approved these changes
Jan 16, 2026
rockhowse
approved these changes
Jan 16, 2026
Contributor
rockhowse
left a comment
There was a problem hiding this comment.
Approved but asked a question about an unexpected change as I am not sure what exactly is required for it to work (thought the forward-merger behavior was a typescript bot 🤔 )
Member
Author
|
/merge |
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
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.
I just merged #347 into
release/26.02and after a few minutes hadn't seen it forward-merged tomain.Looks like automatic forward mergers are not set up here. They should be, now that we're producing RAPIDS-versioned images (rapidsai/build-planning#187) and using the new RAPIDS branching strategy (#323).
This enables forward mergers.
This also
git cherry-picks over the changes from #347 so they'll make it ontomain.