Update numpy requirement from ~=2.5.0 to ~=2.5.1 (#345)

Updates the requirements on [numpy](https://github.com/numpy/numpy) to
permit the latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/numpy/numpy/releases">numpy's
releases</a>.</em></p>
<blockquote>
<h2>v2.5.1 (July 4, 2026)</h2>
<h1>NumPy 2.5.1 Release Notes</h1>
<p>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.</p>
<p>This release supports Python versions 3.12-3.14</p>
<h2>Changes</h2>
<ul>
<li>
<p>The minimum supported GCC version has been updated from 9.3.0 to
10.3.0</p>
<p>(<a
href="https://redirect.github.com/numpy/numpy/pull/31843">gh-31843</a>)</p>
</li>
</ul>
<h2>Contributors</h2>
<p>A total of 10 people contributed to this release. People with a
&quot;+&quot; by their
names contributed a patch for the first time.</p>
<ul>
<li>Adhyan Gupta +</li>
<li>Ankit Ahlawat</li>
<li>Charles Harris</li>
<li>Iason Krommydas</li>
<li>Joren Hammudoglu</li>
<li>Kumar Aditya</li>
<li>Nathan Goldbaum</li>
<li>Sebastian Berg</li>
<li>Ties Jan Hefting +</li>
<li>Vineet Kumar</li>
</ul>
<h2>Pull requests merged</h2>
<p>A total of 20 pull requests were merged for this release.</p>
<ul>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31707">#31707</a>:
MAINT: Prepare 2.5.x for further development</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31721">#31721</a>:
CI: fix new <code>cython-lint</code> errors (<a
href="https://redirect.github.com/numpy/numpy/issues/31711">#31711</a>)</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31723">#31723</a>:
MAINT: Update meson to match main</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31729">#31729</a>:
TST: use setup-sde instead of curl to get SDE binaries (<a
href="https://redirect.github.com/numpy/numpy/issues/31727">#31727</a>)</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31829">#31829</a>:
BUG: Relax finfo to be easier accessible for all user dtypes...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31831">#31831</a>:
TYP: Fix <code>flatiter.__next__</code> return type for
<code>object_</code> and...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31832">#31832</a>:
BUG: avoid deadlocks using NpyString API (<a
href="https://redirect.github.com/numpy/numpy/issues/31682">#31682</a>)</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31833">#31833</a>:
BUG: fix out array leak in reduceat and accumulate when dtype...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31835">#31835</a>:
BUG: fix numpy datetime cython APIs to be compatible with older...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31836">#31836</a>:
TYP: Fix incorrect dtype inference of <code>asarray([])</code> (<a
href="https://redirect.github.com/numpy/numpy/issues/31732">#31732</a>)</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31837">#31837</a>:
TYP: Fix <code>np.ma.masked_array</code> 2.5.0 regression</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31838">#31838</a>:
FIX: Refactor error handling in array_setstate to prevent
typecode...</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31839">#31839</a>:
TST: xfail multithreaded BLAS test more generously</li>
<li><a
href="https://redirect.github.com/numpy/numpy/pull/31840">#31840</a>:
MAINT: Rename subroutine for crackfortran tests</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst">numpy's
changelog</a>.</em></p>
<blockquote>
<p>This is a walkthrough of the NumPy 2.4.0 release on Linux, which will
be the
first feature release using the <code>numpy/numpy-release
&lt;https://github.com/numpy/numpy-release&gt;</code>__ repository.</p>
<p>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:<code>general release guide &lt;prepare_release&gt;</code>.</p>
<h1>Facility preparation</h1>
<p>Before beginning to make a release, use the
<code>requirements/*_requirements.txt</code> 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:</p>
<ul>
<li>Git can be set up to use a keyring to store your GitHub personal
access token.
Search online for the details.</li>
</ul>
<h1>Prior to release</h1>
<h2>Add/drop Python versions</h2>
<p>When adding or dropping Python versions, multiple config and CI files
need to
be edited in addition to changing the minimum version in
<code>pyproject.toml</code>.
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.</p>
<h2>Backport pull requests</h2>
<p>Changes that have been marked for this release must be backported to
the
maintenance/2.4.x branch.</p>
<h2>Update 2.4.0 milestones</h2>
<p>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.</p>
<h2>Check the numpy-release repo</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/numpy/numpy/commit/5e1d03ffac5f2c0a9c39bfcaa9fc853b2b83151e"><code>5e1d03f</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/31863">#31863</a>
from charris/prepare-2.5.1</li>
<li><a
href="https://github.com/numpy/numpy/commit/ad0b66b8bf1faedc727d8a80ec217bdc95a3037e"><code>ad0b66b</code></a>
REL: Prepare for the NumPy 2.5.1 release.</li>
<li><a
href="https://github.com/numpy/numpy/commit/9df8516d6c933927b3bb9a7b8fd10f523e627ffd"><code>9df8516</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/31858">#31858</a>
from charris/backport-31688</li>
<li><a
href="https://github.com/numpy/numpy/commit/4dee265afc098a296a62666f6356d4927b67848f"><code>4dee265</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/31857">#31857</a>
from charris/backport-31775</li>
<li><a
href="https://github.com/numpy/numpy/commit/dc8d5530eb0bb3198bfc0538e28d1f284f6f4a80"><code>dc8d553</code></a>
Merge pull request <a
href="https://redirect.github.com/numpy/numpy/issues/31856">#31856</a>
from charris/backport-31846</li>
<li><a
href="https://github.com/numpy/numpy/commit/67cb4a874e7c52d90176ca7343e208dfa3f11d11"><code>67cb4a8</code></a>
fix:Signed integer overflow in datetime.c (<a
href="https://redirect.github.com/numpy/numpy/issues/31688">#31688</a>)</li>
<li><a
href="https://github.com/numpy/numpy/commit/baa2589a94a93b4216159817fe891c83a39eb36d"><code>baa2589</code></a>
TST: Clean up imports, formatting, and assertions</li>
<li><a
href="https://github.com/numpy/numpy/commit/2fe5ba41f935065305cfb31a561202188953c7e9"><code>2fe5ba4</code></a>
TEST: Refactor tests to use np.testing.assert_raises_regex per
review</li>
<li><a
href="https://github.com/numpy/numpy/commit/bb465819882f84304ecbfd180f00bd748f783134"><code>bb46581</code></a>
MAINT: Remove deprecated Python recursion fix</li>
<li><a
href="https://github.com/numpy/numpy/commit/8f34214a5e6e813bea56fec2cdc9bc8ac79ff38b"><code>8f34214</code></a>
MAINT: Move SeedSequence recursion guard to C-layer and add tests</li>
<li>Additional commits viewable in <a
href="https://github.com/numpy/numpy/compare/v2.5.0...v2.5.1">compare
view</a></li>
</ul>
</details>
<br />


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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Author: DefinetlyNotAI

requirements.txt

@@ -6,7 +6,7 @@ DateTime~=6.0
 colorlog~=6.10.1
 aiofiles~=25.1.0
 joblib~=1.5.3
-numpy~=2.5.0
+numpy~=2.5.1
 pathlib~=1.0.1
 tqdm~=4.68.3
 safetensors~=0.8.0