Update numpy requirement from <2.4,>=2.2.0 to >=2.2.0,<2.5

[dependabot]

Updates the requirements on numpy to permit the latest version.

Release notes

Sourced from numpy's releases.

2.4.0 (Dec 20, 2025)

NumPy 2.4.0 Release Notes

The NumPy 2.4.0 release continues the work to improve free threaded Python support, user dtypes implementation, and annotations. There are many expired deprecations and bug fixes as well.

This release supports Python versions 3.11-3.14

Highlights

Apart from annotations and same_value kwarg, the 2.4 highlights are mostly of interest to downstream developers. They should help in implementing new user dtypes.

• Many annotation improvements. In particular, runtime signature introspection.
• New casting kwarg 'same_value' for casting by value.
• New PyUFunc_AddLoopsFromSpec function that can be used to add user sort loops using the ArrayMethod API.
• New __numpy_dtype__ protocol.

Deprecations

Setting the strides attribute is deprecated

Setting the strides attribute is now deprecated since mutating an array is unsafe if an array is shared, especially by multiple threads. As an alternative, you can create a new view (no copy) via:

• np.lib.stride_tricks.strided_window_view if applicable,
• np.lib.stride_tricks.as_strided for the general case,
• or the np.ndarray constructor (buffer is the original array) for a light-weight version.

(gh-28925)

Positional out argument to np.maximum, np.minimum is deprecated

Passing the output array out positionally to numpy.maximum and numpy.minimum is deprecated. For example, np.maximum(a, b, c) will emit a deprecation warning, since c is treated as the output buffer rather than a third input.

Always pass the output with the keyword form, e.g. np.maximum(a, b, out=c). This makes intent clear and simplifies type annotations.

(gh-29052)

align= must be passed as boolean to np.dtype()

... (truncated)

Changelog

Sourced from numpy's changelog.

Update 2.4.0 milestones

Look at the issues/prs with 2.4.0 milestones and either push them off to a later version, or maybe remove the milestone. You may need to add a milestone.

Check the numpy-release repo

The things to check are the cibuildwheel version in .github/workflows/wheels.yml and the openblas versions in openblas_requirements.txt.

Make a release PR

Four documents usually need to be updated or created for the release PR:

• The changelog
• The release notes
• The .mailmap file
• The pyproject.toml file

These changes should be made in an ordinary PR against the maintenance branch. Other small, miscellaneous fixes may be part of this PR. The commit message might be something like::

REL: Prepare for the NumPy 2.4.0 release

Create 2.4.0-changelog.rst.
Update 2.4.0-notes.rst.
Update .mailmap.
Update pyproject.toml

Set the release version

Check the pyproject.toml file and set the release version and update the classifier if needed::

$ gvim pyproject.toml

Check the doc/source/release.rst file

make sure that the release notes have an entry in the release.rst file::

... (truncated)

Commits

• c5ab79c Merge pull request #30487 from charris/prepare-2.4.0.2
• 05e379a REL: Prepare for the NumPy 2.4.0 release (2)
• 485f1c4 REL: Prepare for the NumPy 2.4.0 release (1) (#30486)
• c683481 REL: Prepare for the NumPy 2.4.0 release (#30439)
• 11d9ed2 Merge pull request #30459 from charris/backport-30456
• 2a17ddb TYP: restore generic.__hash__ (#30456)
• d04a429 Merge pull request #30432 from charris/backport-30426
• f94a148 fix more data races in mtrand.pyx (#30426)
• 06a9d42 Merge pull request #30420 from charris/backport-30418
• 30819cd Merge pull request #30419 from charris/backport-30373
• Additional commits viewable in compare view

Dependabot 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 3 package(s) with unknown licenses.

See the Details below.

License Issues

pyproject.toml

Package	Version	License	Issue Type
numpy	>= 2.2.0,< 2.5	Null	Unknown License

requirements.txt

Package	Version	License	Issue Type
numpy	>= 2.2.0,< 2.5	Null	Unknown License

setup.py

Package	Version	License	Issue Type
numpy	>= 2.2.0,< 2.5	Null	Unknown License

Denied Licenses: GPL-1.0-or-later, LGPL-2.0-or-later

OpenSSF Scorecard

Package	Version	Score	Details
pip/numpy	>= 2.2.0,< 2.5	🟢 7.2	Details Check Score Reason Maintained 🟢 10 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10 Dependency-Update-Tool 🟢 10 update tool detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Code-Review 🟢 10 all changesets reviewed Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 3 dependency not pinned by hash detected -- score normalized to 3 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 9 license file detected Vulnerabilities ⚠️ 0 24 existing vulnerabilities detected Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. Fuzzing 🟢 10 project is fuzzed SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 3 branch protection is not maximal on development and all release branches Security-Policy 🟢 9 security policy file detected CI-Tests 🟢 10 26 out of 26 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 101 contributing companies or organizations
pip/numpy	>= 2.2.0,< 2.5	🟢 7.2	Details Check Score Reason Maintained 🟢 10 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10 Dependency-Update-Tool 🟢 10 update tool detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Code-Review 🟢 10 all changesets reviewed Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 3 dependency not pinned by hash detected -- score normalized to 3 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 9 license file detected Vulnerabilities ⚠️ 0 24 existing vulnerabilities detected Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. Fuzzing 🟢 10 project is fuzzed SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 3 branch protection is not maximal on development and all release branches Security-Policy 🟢 9 security policy file detected CI-Tests 🟢 10 26 out of 26 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 101 contributing companies or organizations
pip/numpy	>= 2.2.0,< 2.5	🟢 7.2	Details Check Score Reason Maintained 🟢 10 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10 Dependency-Update-Tool 🟢 10 update tool detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Code-Review 🟢 10 all changesets reviewed Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies 🟢 3 dependency not pinned by hash detected -- score normalized to 3 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 9 license file detected Vulnerabilities ⚠️ 0 24 existing vulnerabilities detected Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. Fuzzing 🟢 10 project is fuzzed SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 3 branch protection is not maximal on development and all release branches Security-Policy 🟢 9 security policy file detected CI-Tests 🟢 10 26 out of 26 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 101 contributing companies or organizations

Scanned Files

• pyproject.toml
• requirements.txt
• setup.py