build(deps): update numpy requirement from <1.27.0,>=1.17.2 to >=1.17.2,<2.4.0 in /requirements

[dependabot]

Updates the requirements on numpy to permit the latest version.

Release notes

Sourced from numpy's releases.

v2.3.2 (Jul 24, 2025)

NumPy 2.3.2 Release Notes

The NumPy 2.3.2 release is a patch release with a number of bug fixes and maintenance updates. The highlights are:

• Wheels for Python 3.14.0rc1
• PyPy updated to the latest stable release
• OpenBLAS updated to 0.3.30

This release supports Python versions 3.11-3.14

Contributors

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

• !DWesl
• Charles Harris
• Joren Hammudoglu
• Maanas Arora
• Marco Edward Gorelli
• Matti Picus
• Nathan Goldbaum
• Sebastian Berg
• kostayScr +

Pull requests merged

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

• #29256: MAINT: Prepare 2.3.x for further development
• #29283: TYP: Work around a mypy issue with bool arrays (#29248)
• #29284: BUG: fix fencepost error in StringDType internals
• #29287: BUG: handle case in mapiter where descriptors might get replaced...
• #29350: BUG: Fix shape error path in array-interface
• #29412: BUG: Allow reading non-npy files in npz and add test
• #29413: TST: Avoid uninitialized values in test (#29341)
• #29414: BUG: Fix reference leakage for output arrays in reduction functions
• #29415: BUG: fix casting issue in center, ljust, rjust, and zfill (#29369)
• #29416: TYP: Fix overloads in np.char.array and np.char.asarray...
• #29417: BUG: Any dtype should call square on arr \*\* 2 (#29392)
• #29424: MAINT: use a stable pypy release in CI
• #29425: MAINT: Support python 314rc1
• #29429: MAINT: Update highway to match main.
• #29430: BLD: use github to build macos-arm64 wheels with OpenBLAS and...
• #29437: BUG: fix datetime/timedelta hash memory leak (#29411)

Checksums

... (truncated)

Changelog

Sourced from numpy's changelog.

This is a walkthrough of the NumPy 2.1.0 release on Linux, modified for building with GitHub Actions and cibuildwheels and uploading to the anaconda.org staging repository for NumPy <https://anaconda.org/multibuild-wheels-staging/numpy>_. The commands can be copied into the command line, but be sure to replace 2.1.0 by 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.
• You can use the keyring app to store the PyPI password for twine. See the online twine documentation for details.

Prior to release

Add/drop Python versions

When adding or dropping Python versions, two files need to be edited:

• .github/workflows/wheels.yml # for github cibuildwheel
• pyproject.toml # for classifier and minimum version check.

Make these changes in an ordinary PR against main and backport if necessary. Add [wheel build] at the end of the title line of the commit summary so that wheel builds will be run to test the changes. We currently release wheels for new Python versions after the first Python rc once manylinux and cibuildwheel support it.

Backport pull requests

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

Update 2.1.0 milestones

... (truncated)

Commits

• bc5e4f8 Merge pull request #29438 from charris/prepare-2.3.2
• 4bc5960 REL: Prepare for the NumPy 2.3.2 release [wheel build]
• 2679276 Merge pull request #29437 from charris/backport-29411
• b0fa284 BUG: fix datetime/timedelta hash memory leak (#29411)
• 6700579 Merge pull request #29425 from charris/support-python-314rc1
• 40aa44d BUILD: Add Python 3.14 to wheel builds [wheel build]
• 968fa73 Merge pull request #29430 from charris/backport-29069
• 6ad9db9 Merge pull request #29429 from charris/update-highway
• 3584ddd MAINT: Update highway to match main.
• f78821f BLD: use github to build macos-arm64 wheels with OpenBLAS [wheel build]
• 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)

---

📚 Documentation preview 📚: https://pytorch-lightning--21081.org.readthedocs.build/en/21081/

[Borda]

let see if we still need this pin

[Borda]

@dependabot rebase

[github-actions]

⛈️ Required checks status: Has failure 🔴

Warning
This job will need to be re-run to merge your PR. If you do not have write access to the repository, you can ask Lightning-AI/lai-frameworks to re-run it. If you push a new commit, all of CI will re-trigger.

Groups summary

🔴 pytorch_lightning: Tests workflow

Check ID	Status
pl-cpu-guardian	failure	❌

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/test.txt.

🔴 pytorch_lightning: Azure GPU

Check ID	Status
pytorch-lightning (GPUs) (testing Lightning | latest)	success	✅
pytorch-lightning (GPUs) (testing PyTorch | oldest)	failure	❌
pytorch-lightning (GPUs) (testing PyTorch | latest)	success	✅

These checks are required after the changes to requirements/pytorch/test.txt, requirements/fabric/test.txt.

🟢 pytorch_lightning: Benchmarks

Check ID	Status
lightning.Benchmarks	success	✅

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/test.txt.

🟢 fabric: Docs

Check ID	Status
docs-make (fabric, doctest)	success	✅
docs-make (fabric, html)	success	✅

These checks are required after the changes to requirements/fabric/test.txt.

🟢 pytorch_lightning: Docs

Check ID	Status
docs-make (pytorch, doctest)	success	✅
docs-make (pytorch, html)	success	✅

These checks are required after the changes to requirements/pytorch/test.txt.

🟢 pytorch_lightning: Docker

Check ID	Status
build-cuda (3.10, 2.1.2, 12.1.1)	success	✅
build-cuda (3.11, 2.2.2, 12.1.1)	success	✅
build-cuda (3.11, 2.3.1, 12.1.1)	success	✅
build-cuda (3.11, 2.4.1, 12.1.1)	success	✅
build-cuda (3.12, 2.5.1, 12.1.1)	success	✅
build-cuda (3.12, 2.6.0, 12.4.1)	success	✅
build-pl (3.10, 2.1, 12.1.1)	success	✅
build-pl (3.11, 2.2, 12.1.1)	success	✅
build-pl (3.11, 2.3, 12.1.1)	success	✅
build-pl (3.11, 2.4, 12.1.1)	success	✅
build-pl (3.12, 2.5, 12.1.1)	success	✅
build-pl (3.12, 2.6, 12.4.1)	success	✅
build-pl (3.12, 2.7, 12.6.3)	success	✅
build-pl (3.12, 2.8, 12.6.3, true)	success	✅

These checks are required after the changes to requirements/pytorch/test.txt, requirements/fabric/test.txt.

🔴 lightning_fabric: CPU workflow

Check ID	Status
fabric-cpu-guardian	failure	❌

These checks are required after the changes to requirements/fabric/test.txt.

🔴 lightning_fabric: Azure GPU

Check ID	Status
lightning-fabric (GPUs) (testing Fabric | oldest)	failure	❌
lightning-fabric (GPUs) (testing Fabric | latest)	success	✅
lightning-fabric (GPUs) (testing Lightning | latest)	success	✅

These checks are required after the changes to requirements/fabric/test.txt.

🟢 mypy

Check ID	Status
mypy	success	✅

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/test.txt.

🟢 install

Check ID	Status
install-pkg-guardian	success	✅

These checks are required after the changes to requirements/fabric/test.txt, requirements/pytorch/test.txt.

---

Thank you for your contribution! 💜

Note
This comment is automatically generated and updates for 60 minutes every 180 seconds. If you have any other questions, contact carmocca for help.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86%. Comparing base (9ca360b) to head (7ccf969).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #21081    +/-   ##
========================================
- Coverage      87%      86%    -1%     
========================================
  Files         269      269            
  Lines       23501    23501            
========================================
- Hits        20487    20285   -202     
- Misses       3014     3216   +202