Bump numpy from 2.2.6 to 2.5.3

[dependabot]

Bumps numpy from 2.2.6 to 2.5.3.

Release notes

Sourced from numpy's releases.

v2.5.3 (Sep 6, 2026)

NumPy 2.5.3 Release Notes

The NumPy 2.5.3 is a patch release that fixes bugs discovered after the 2.5.2 release. Apart from the usual bug and maintenance work, there are a number of StringDType related fixes for problems discovered during the ongoing string work in the main branch.

This release supports Python versions 3.12-3.15

Changes

• Casting a fixed-width byte string array (np.bytes_) to StringDType now raises TypeError when the bytes are not valid UTF-8. Previously the invalid bytes were stored as-is and later caused undefined behavior in string operations.

  (gh-32296)

• MaskedArray._fill_value would become stale when ufuncs that change dtype left the result holding a fill_value typed for the old dtype. The mismatch was silent until something later called _check_fill_value, such as .view(), and then a TypeError would be raised. Now, when the copied fill_value is no longer valid for the new dtype, fall back to the default fill_value for that dtype instead of propagating the stale value. This may raise a ComplexWarning if the fill_value is complex and the new dtype is real.

  (gh-32423)

Contributors

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

• Charles Harris
• Iason Krommydas
• James Davies +
• Joren Hammudoglu
• Maanas Arora
• Matti Picus
• Nathan Goldbaum
• Shikhar Goel +
• Yeonho Kim +

Pull requests merged

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

• #32235: MAINT: Prepare 2.5.x for further development

... (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

• dd88c0c Merge pull request #32511 from charris/prepare-2.5.3
• edcac6a REL: Prepare for the NumPy 2.5.3 release
• fd4d908 Merge pull request #32509 from charris/backport-32496
• 65bb1da BUG: fix crash in ufunc.resolve_dtypes with a Python scalar type (#32496)
• 294956e Merge pull request #32506 from charris/backport-32503
• 26428d9 DOC: fix scipy docs links in intersphinx mapping (#32507)
• 5fab1cb DOC: use static scipy doc site for intershpinx (#32503)
• 7beed2f Merge pull request #32481 from ngoldbaum/stringdtype-backport
• 8972f70 Merge pull request #32478 from charris/backport-32466
• ab1b589 Merge pull request #32477 from charris/backport-32423
• Additional commits viewable in compare view

[villelaitila]

Potential Python-version compatibility issue: numpy 2.5.2 declares Requires-Python: >=3.12 on PyPI (numpy dropped support for Python <3.12 a few releases back). This repo's setup.cfg still advertises python_requires = >=3.8 and lists classifiers down to Python 3.8, and requirements.txt (used for pip install -r requirements.txt per CLAUDE.md's dev setup) directly pins numpy==2.5.2.

That means pip install -r requirements.txt will fail to resolve on Python 3.8–3.11, which the package still claims to support. A few options:

• If the project no longer intends to support <3.12, this is a good moment to bump python_requires/classifiers in setup.cfg accordingly (in a follow-up, since Dependabot won't touch that file).
• Otherwise, this bump should be capped (e.g. numpy<2.5 or an explicit sys_platform/python_version marker) so contributors on older-but-still-supported Python versions aren't broken.

Note numpy isn't in setup.cfg's install_requires (only pandas, lxml, Levenshtein are) — it's pulled in transitively via pandas and used directly only in src/sgraph/cypher.py — so published-package consumers aren't directly affected by this pin; the risk is scoped to requirements.txt-based dev/CI installs on older Python.

No other issues spotted — this is a minimal, mechanical version bump otherwise.

---

Generated by Claude Code

[dependabot]

Superseded by #207.