Skip to content

Bump numpy cap in CI requirements to 2.5.4 - #4072

Open
T4rk1n wants to merge 1 commit into
devfrom
ci/bump-numpy
Open

T4rk1n wants to merge 1 commit into
devfrom
ci/bump-numpy

Conversation

@T4rk1n

@T4rk1n T4rk1n commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the numpy cap in requirements/ci.txt from <=2.2.6 to <=2.5.4.

The old cap kept CI on a numpy without Python 3.14 wheels, so we never tested the numpy 2.5 that users get on 3.13/3.14. It also gets copied into downstream packages: Anaconda's defaults dash recipe puts our ci extra in run_constrained, so an old numpy pin there makes Dash impossible to install with numpy on 3.13/3.14.

Resolution with uv pip compile requirements/ci.txt:

  • 3.9: numpy 2.0.2 (2.1+ dropped 3.9)
  • 3.12 / 3.14: numpy 2.5.4, pandas 3.0.6

Checked locally with numpy 2.5.4: cbsc018 and async_cbsc018 (ndarray callback output) and tests/unit/mcp/tools/test_mcp_callback_adapter.py pass.

numpy<=2.2.6 kept CI on a numpy that has no Python 3.14 wheels and
never tested the numpy 2.5 that users get on 3.13/3.14. Python 3.9 jobs
still resolve to numpy 2.0.2.
@sonarqubecloud

Copy link
Copy Markdown

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