Skip to content

enable forward mergers#350

Merged
rapids-bot[bot] merged 2 commits intorapidsai:mainfrom
jameslamb:enable-forward-mergers
Jan 16, 2026
Merged

enable forward mergers#350
rapids-bot[bot] merged 2 commits intorapidsai:mainfrom
jameslamb:enable-forward-mergers

Conversation

@jameslamb
Copy link
Member

@jameslamb jameslamb commented Jan 15, 2026

I just merged #347 into release/26.02 and after a few minutes hadn't seen it forward-merged to main.

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 onto main.

@jameslamb jameslamb requested a review from a team as a code owner January 15, 2026 23:50
@jameslamb jameslamb added improvement Improves an existing functionality non-breaking Introduces a non-breaking change labels Jan 15, 2026
Copy link
Contributor

@rockhowse rockhowse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 🤔 )

@jameslamb
Copy link
Member Author

/merge

@rapids-bot rapids-bot bot merged commit 6d29e9c into rapidsai:main Jan 16, 2026
1533 of 1550 checks passed
@jameslamb jameslamb deleted the enable-forward-mergers branch January 16, 2026 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants