chore(deps): update numpy requirement from <2.4,>=2 to >=2,<2.5 - #246
Merged
Merged
Conversation
Updates the requirements on [numpy](https://github.com/numpy/numpy) to permit the latest version. - [Release notes](https://github.com/numpy/numpy/releases) - [Changelog](https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst) - [Commits](numpy/numpy@v2.0.0...v2.4.6) --- updated-dependencies: - dependency-name: numpy dependency-version: 2.4.6 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
added
the
dependencies
DORA Metrics
|
The `numpy>=2,<2.4` ceiling arrived on 2026-07-23 (71c41c3) explained as "NumPy 2.4+ bundles PEP 695 syntax in its stubs; mypy targeting the supported Python 3.11 floor cannot parse those stubs." Dependabot has been proposing the widening since 2026-08-23; the PR could not merge because Dependabot edits pyproject.toml without regenerating uv.lock, so the lock-check gate fails (CONTRIBUTING.md documents the manual step). Bringing the lock along was the moment to check the reason, and it does not hold for the released 2.4 line: numpy 2.4.0 and 2.4.6 wheels each ship 264 .pyi files, and none of them contains a PEP 695 `type` statement or a PEP 695 generic parameter list. The mypy half is true and worth keeping in view -- mypy 2.2.0 at --python-version 3.11 still rejects `type Alias = int` with "Type statement is only supported in Python 3.12 and greater [syntax]" -- so the comment now says that a stub release using one turns lint red, rather than naming a version that never did. What does hold is a harder constraint the old comment did not mention: numpy 2.5.0 requires Python >=3.12, and 3.11 is a supported floor here (pyproject `environments` pins the resolution to 3.11-3.13). `<2.5` is therefore what keeps the lock resolvable, not a preference. uv.lock moves numpy 2.3.5 -> 2.4.6 rather than only widening the range: a ceiling raised without moving the pin claims compatibility that nothing tests. requirements-docker.lock is unchanged -- numpy is in `dev`, which the cloud/postgres export does not include, and `src/` imports numpy nowhere. Verified locally with numpy 2.4.6 installed: `mypy src/ --ignore-missing-imports` (the exact lint-job command) reports "Success: no issues found in 157 source files", `uv lock --check` passes (256 packages), `uv export` leaves requirements-docker.lock untouched, and tests/unit/test_windows_shard_thread_pinning.py -- the only test that imports numpy -- passes (8 passed). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018ybRVCaL1Lyd9d5kFTndh3
Owner
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
brownjuly2003-code
deleted the
dependabot/pip/numpy-gte-2-and-lt-2.5
branch
September 11, 2026 03:03
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
2 participants
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.
Updates the requirements on numpy to permit the latest version.
Release notes
Sourced from numpy's releases.
Changelog
Sourced from numpy's changelog.
... (truncated)
Commits
b832a09Merge pull request #31462 from charris/prepare-2.4.657cc147REL: Prepare for the NumPy 2.4.6 release0c72b0bMerge pull request #31459 from charris/backport-313479778d26BUG: core: Don't call INCREF/DECREF on descr in NpyStringAcquireAllocator. (#...e0e3876BUG: core: Don't call INCREF/DECREF on descr in NpyStringAcquireAllocator. (#...d1bffebBUG:np.linalg.svd(..., hermitian=True)returns non-unitaryvh(#31347)8d8d7e5Merge pull request #31453 from seberg/issue-31452bddaab7BUG: Fix regression inarr.conj()37a1eccMerge pull request #31444 from charris/begin-2.4.63c0e043MAINT: Prepare 2.4.x for further developmentDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)