Update numpy requirement from >=1.24 to >=2.5.1

[dependabot]

Updates the requirements on numpy to permit the latest version.

Release notes

Sourced from numpy's releases.

v2.5.1 (July 4, 2026)

NumPy 2.5.1 Release Notes

The NumPy 2.5.1 is a patch release that fixes bugs discovered after the 2.5.0 release. The most noticeable is the fix is to the numpy datetime cython API which should allow downstream to support NumPy versions older than 2.5. Preparation for Python 3.15 continues along with typing improvements.

This release supports Python versions 3.12-3.14

Changes

• The minimum supported GCC version has been updated from 9.3.0 to 10.3.0

  (gh-31843)

Contributors

A total of 10 people contributed to this release. People with a "+" by their names contributed a patch for the first time.

• Adhyan Gupta +
• Ankit Ahlawat
• Charles Harris
• Iason Krommydas
• Joren Hammudoglu
• Kumar Aditya
• Nathan Goldbaum
• Sebastian Berg
• Ties Jan Hefting +
• Vineet Kumar

Pull requests merged

A total of 20 pull requests were merged for this release.

• #31707: MAINT: Prepare 2.5.x for further development
• #31721: CI: fix new cython-lint errors (#31711)
• #31723: MAINT: Update meson to match main
• #31729: TST: use setup-sde instead of curl to get SDE binaries (#31727)
• #31829: BUG: Relax finfo to be easier accessible for all user dtypes...
• #31831: TYP: Fix flatiter.__next__ return type for object_ and...
• #31832: BUG: avoid deadlocks using NpyString API (#31682)
• #31833: BUG: fix out array leak in reduceat and accumulate when dtype...
• #31835: BUG: fix numpy datetime cython APIs to be compatible with older...
• #31836: TYP: Fix incorrect dtype inference of asarray([]) (#31732)
• #31837: TYP: Fix np.ma.masked_array 2.5.0 regression
• #31838: FIX: Refactor error handling in array_setstate to prevent typecode...
• #31839: TST: xfail multithreaded BLAS test more generously
• #31840: MAINT: Rename subroutine for crackfortran tests

... (truncated)

Changelog

Sourced from numpy's changelog.

This is a walkthrough of the NumPy 2.4.0 release on Linux, which will be the first feature release using the numpy/numpy-release <https://github.com/numpy/numpy-release>__ repository.

The commands can be copied into the command line, but be sure to replace 2.4.0 with the correct version. This should be read together with the :ref:general release guide <prepare_release>.

Facility preparation

Before beginning to make a release, use the requirements/*_requirements.txt files to ensure that you have the needed software. Most software can be installed with pip, but some will require apt-get, dnf, or whatever your system uses for software. You will also need a GitHub personal access token (PAT) to push the documentation. There are a few ways to streamline things:

• Git can be set up to use a keyring to store your GitHub personal access token. Search online for the details.

Prior to release

Add/drop Python versions

When adding or dropping Python versions, multiple config and CI files need to be edited in addition to changing the minimum version in pyproject.toml. Make these changes in an ordinary PR against main and backport if necessary. We currently release wheels for new Python versions after the first Python RC once manylinux and cibuildwheel support that new Python version.

Backport pull requests

Changes that have been marked for this release must be backported to the maintenance/2.4.x branch.

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

... (truncated)

Commits

• 5e1d03f Merge pull request #31863 from charris/prepare-2.5.1
• ad0b66b REL: Prepare for the NumPy 2.5.1 release.
• 9df8516 Merge pull request #31858 from charris/backport-31688
• 4dee265 Merge pull request #31857 from charris/backport-31775
• dc8d553 Merge pull request #31856 from charris/backport-31846
• 67cb4a8 fix:Signed integer overflow in datetime.c (#31688)
• baa2589 TST: Clean up imports, formatting, and assertions
• 2fe5ba4 TEST: Refactor tests to use np.testing.assert_raises_regex per review
• bb46581 MAINT: Remove deprecated Python recursion fix
• 8f34214 MAINT: Move SeedSequence recursion guard to C-layer and add tests
• 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 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)

[Ben05-sys]

Closing: the floors in requirements.txt are deliberately low so the terminal installs against the pandas/numpy someone already has, and the code uses nothing these releases added. Raising them would drop users on the older line to buy nothing. Dependabot's pip strategy is now increase-if-necessary (deaa526), so floors move only when the declared range genuinely cannot resolve — the exact pin in requirements-dev.txt still tracks upstream.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.