Update to latest version (#2273293)

0002-Unpin-NumPy-build-requirement.patch

@@ -1,4 +1,4 @@
-From 789bb69a3175c6ecc03449128d72cac63522d98f Mon Sep 17 00:00:00 2001
+From 05484ecf85b7f9ca67da454a4147098023626a81 Mon Sep 17 00:00:00 2001
 From: Elliott Sales de Andrade <quantum.analyst@gmail.com>
 Date: Fri, 11 Aug 2023 02:36:06 -0400
 Subject: [PATCH 2/5] Unpin NumPy build requirement
@@ -9,22 +9,33 @@ run against a version different from the one it was built against.
 
 Signed-off-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
 ---
- pyproject.toml | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
+ pyproject.toml | 13 +------------
+ 1 file changed, 1 insertion(+), 12 deletions(-)
 
 diff --git a/pyproject.toml b/pyproject.toml
-index 7131609c63..e76ec736d7 100644
+index 44f56d8cc1..33ce124527 100644
 --- a/pyproject.toml
 +++ b/pyproject.toml
-@@ -2,7 +2,7 @@
- build-backend = "setuptools.build_meta"
- requires = [
-     "certifi>=2020.06.20",
--    "numpy>=1.25",
-+    "numpy",
+@@ -5,18 +5,7 @@ requires = [
      "pybind11>=2.6",
      "setuptools>=64",
      "setuptools_scm>=7",
+-
+-    # Comments on numpy build requirement range:
+-    #
+-    #   1. >=2.0.x is the numpy requirement for wheel builds for distribution
+-    #      on PyPI - building against 2.x yields wheels that are also
+-    #      ABI-compatible with numpy 1.x at runtime.
+-    #   2. Note that building against numpy 1.x works fine too - users and
+-    #      redistributors can do this by installing the numpy version they like
+-    #      and disabling build isolation.
+-    #   3. The <2.3 upper bound is for matching the numpy deprecation policy,
+-    #      it should not be loosened.
+-    "numpy>=2.0.0rc1,<2.3",
++    "numpy",
+ ]
+ 
+ [tool.setuptools_scm]
 -- 
-2.41.0
+2.43.0