deps: update numpy requirement from >=1.21 to >=2.2.6 - #29
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
This was referenced Aug 27, 2026
dependabot
Bot
force-pushed
the
dependabot/pip/numpy-gte-2.2.6
branch
from
August 27, 2026 13:02
7745da6 to
69a568c
Compare
dependabot
Bot
force-pushed
the
dependabot/pip/numpy-gte-2.2.6
branch
from
September 18, 2026 18:57
69a568c to
637750a
Compare
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@v1.21.0...v2.2.6) --- updated-dependencies: - dependency-name: numpy dependency-version: 2.2.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/pip/numpy-gte-2.2.6
branch
from
September 18, 2026 20:31
637750a to
dae704e
Compare
DenisDrobyshev
added a commit
that referenced
this pull request
Sep 20, 2026
My own change in #23 left these two on update-types: ["version-update: semver-major"], which does not do what it looks like it does. #29 raised numpy from >=1.21 to >=2.2.6 and walked straight past it, because for a `>=` constraint Dependabot files a "requirement update" rather than a version update - the behaviour already written into lemma's configuration and which I copied only half of. pytest joins mypy for the other reason: pytest 9 requires Python >=3.10 and mypy 2.3 requires >=3.11, so both fail the 3.9 leg at install. Ignoring them is a holding action, not an answer - #30 is about the support matrix that is actually causing this.
Contributor
Author
|
Looks like numpy is no longer being updated by Dependabot, so this is no longer needed. |
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
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.
... (truncated)
Commits
2b686f6Merge pull request #28980 from charris/prepare-2.2.6ed41828REL: Prepare for the NumPy 2.2.6 release [wheel build]83e4e7fMerge pull request #28966 from charris/backport-28958248f0cbTYP: add rejection-tests for complexndarrayfloordiv5bad9daTYP: reject complex scalar types inndarray.__ifloordiv__6c42775Merge pull request #28915 from charris/backport-288924277e7cMerge pull request #28916 from charris/backport-28898bd1c863BUG: Fix missing check for PyErr_Occurred() in _pyarray_correlate. (#28898)87d1d8aMAINT: Avoid dereferencing/strict aliasing warnings during complex casts in `...9e50659Merge pull request #28913 from charris/backport-28908