Skip to content

Backport "Drop CuPy pre-13.6.0 logic & fix CuPy 14 compatibility" to 26.02#1037

Merged
jameslamb merged 1 commit intorelease/26.02from
hotfix/26.02.01
Mar 4, 2026
Merged

Backport "Drop CuPy pre-13.6.0 logic & fix CuPy 14 compatibility" to 26.02#1037
jameslamb merged 1 commit intorelease/26.02from
hotfix/26.02.01

Conversation

@jameslamb
Copy link
Member

@jameslamb jameslamb commented Mar 4, 2026

Following the new RAPIDS hotfix process (docs still in progress at rapidsai/docs#716), this backports the following changes to cuCIM 26.02:

See #1036 for more details.

Notes for Reviewers

Once this is merged, I'll release the new state of release/26.02 as cuCIM 26.02.01.

…26.02 (#1036)

Backports PR:

* #1031

From that PR's description

> 
> Fixes #1030
> 
> As part of the upgrade to CUDA 13.0, RAPIDS also updated to CuPy
13.6.0 as a minimum. Therefore the workarounds for CuPy 13.3.0 and
earlier do not apply. So clean them up.
> 
> Should add this same cleanup is needed for CuPy 14 compatibility. So
this fixes cuCIM to work with CuPy 14.
> 
> Lastly CuPy 14.0.0 included a bug that affected some
`__warningregistry__` resetting logic in cuCIM:
#1031 (comment)
> 
> This issue will be fixed in CuPy 14.0.1. So simply excluded CuPy
14.0.0 from the CuPy versions installable with cuCIM.
> 
> Refs:
> 
> * rapidsai/build-planning#208
> * #926
> * cupy/cupy#9704


Also picks up the following nightly CI test fix from earlier today:

* #1035

---------

Co-authored-by: Gregory Lee <grelee@nvidia.com>
@jameslamb jameslamb requested a review from jakirkham March 4, 2026 00:49
@jameslamb jameslamb requested review from a team as code owners March 4, 2026 00:49
@jameslamb jameslamb added improvement Improves an existing functionality non-breaking Introduces a non-breaking change labels Mar 4, 2026
Copy link
Member

@jakirkham jakirkham left a comment

Choose a reason for hiding this comment

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

Thanks James! 🙏

@jameslamb
Copy link
Member Author

I've seen enough passing CI to be confident here (this is testing the exact same commit was tested in #1036, remember). Merging this so we don't have to wait for 2 more arm64 runners to get scheduled.

@jameslamb jameslamb merged commit b03a9a5 into release/26.02 Mar 4, 2026
63 of 66 checks passed
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.

2 participants