build: bump numpy from 1.26.4 to 2.2.0

[dependabot]

Bumps numpy from 1.26.4 to 2.2.0.

Release notes

Sourced from numpy's releases.

2.2.0 (Dec 8, 2024)

NumPy 2.2.0 Release Notes

The NumPy 2.2.0 release is quick release that brings us back into sync with the usual twice yearly release cycle. There have been an number of small cleanups, as well as work bringing the new StringDType to completion and improving support for free threaded Python. Highlights are:

• New functions matvec and vecmat, see below.
• Many improved annotations.
• Improved support for the new StringDType.
• Improved support for free threaded Python
• Fixes for f2py

This release supports Python versions 3.10-3.13.

Deprecations

• _add_newdoc_ufunc is now deprecated. ufunc.__doc__ = newdoc should be used instead.

  (gh-27735)

Expired deprecations

• bool(np.array([])) and other empty arrays will now raise an error. Use arr.size > 0 instead to check whether an array has no elements.

  (gh-27160)

Compatibility notes

• numpy.cov now properly transposes single-row (2d array) design matrices when rowvar=False. Previously, single-row design matrices would return a scalar in this scenario, which is not correct, so this is a behavior change and an array of the appropriate shape will now be returned.

  (gh-27661)

New Features

• New functions for matrix-vector and vector-matrix products

  Two new generalized ufuncs were defined:

  • numpy.matvec - matrix-vector product, treating the arguments as stacks of matrices and column vectors,

... (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, three files need to be edited:

• .github/workflows/wheels.yml # for github cibuildwheel
• tools/ci/cirrus_wheels.yml # for cibuildwheel aarch64/arm64 builds
• 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. For Python 3.11 we were able to release within a week of the rc1 announcement.

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

• e7a123b Merge pull request #27928 from charris/prepare-2.2.0
• d97d071 MAINT: Try fixing MacOS cirrus build failures. [wheel build]
• 1ed7b67 REL: Prepare for the NumPy 2.2.0 release [wheel build]
• fd9e7ef Merge pull request #27916 from charris/backport-27915
• 2e0941f MAINT: Bump actions/cache from 4.1.2 to 4.2.0
• 013656d Merge pull request #27912 from charris/backport-27877
• 7895ba6 Merge pull request #27913 from charris/backport-27896
• ee8d1cd PERF: improve multithreaded ufunc scaling (#27896)
• 77fff6b ENH: Refactor __qualname__ across API (#27877)
• b30a338 Merge pull request #27911 from charris/backport-27891
• 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)

[samjwu]

The conflict is caused by:
The user requested numpy==2.2.0
doxysphinx 3.3.12 depends on numpy<2.0.0 and >=1.26.4

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