Skip to content

ci-wheel: set pip floor to 25.3#347

Merged
jameslamb merged 1 commit intorapidsai:release/26.02from
jameslamb:pip-floor
Jan 15, 2026
Merged

ci-wheel: set pip floor to 25.3#347
jameslamb merged 1 commit intorapidsai:release/26.02from
jameslamb:pip-floor

Conversation

@jameslamb
Copy link
Member

@jameslamb jameslamb commented Jan 15, 2026

Contributes to rapidsai/build-planning#242

To adjust to the new behavior introduced into pip in pypa/pip#13534, we're rolling out changes like rapidsai/cudf#21048 that pass --build-constraint to pip wheel.

That flag is new as of pip>=25.3, so it's important that RAPIDS wheel builds in CI use at least pip>=25.3. That's the version they're already getting today, this PR just gives us a bit of extra protection by making that explicit in the Dockerfile for the ci-wheel image.

Notes for Reviewers

So RAPIDS requires pip>=25.3 now?

No. It's only required to BUILD RAPIDS wheels and only if you're using the CI scripts in RAPIDS repos.

Building them in devcontainers or from source on your own doesn't have this restriction.

Why not update citestwheel too?

Nothing is changing about the versions of pip required for INSTALLING RAPIDS wheels, and there's not a strong relationship between the pip used at build time and the one used at install time.

Why no update ci-conda too?

Conda builds are totally unaffected by the new pip behavior.

@jameslamb jameslamb changed the title WIP: ci-wheel: set pip floor to 25.3 ci-wheel: set pip floor to 25.3 Jan 15, 2026
@jameslamb jameslamb marked this pull request as ready for review January 15, 2026 20:55
@jameslamb jameslamb requested a review from a team as a code owner January 15, 2026 20:55
@jameslamb jameslamb requested review from AyodeAwe and removed request for a team January 15, 2026 20:55
@jameslamb jameslamb changed the base branch from main to release/26.02 January 15, 2026 21:30
@jameslamb jameslamb merged commit ca3168d into rapidsai:release/26.02 Jan 15, 2026
1856 of 1971 checks passed
@jameslamb jameslamb deleted the pip-floor branch January 15, 2026 23:45
@jameslamb jameslamb mentioned this pull request Jan 15, 2026
jameslamb added a commit to jameslamb/ci-imgs that referenced this pull request Jan 15, 2026
rapids-bot bot pushed a commit that referenced this pull request Jan 16, 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-pick`s over the changes from #347 so they'll make it onto `main`.

Authors:
  - James Lamb (https://github.com/jameslamb)

Approvers:
  - Bradley Dice (https://github.com/bdice)
  - Nate Rock (https://github.com/rockhowse)

URL: #350
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants