Freezing the maximum NumPy version to 1.23.5 (#1035)

And fixing coveralls.io LCOV dependency issue

.github/workflows/coverage.yaml

@@ -35,7 +35,9 @@ jobs:
         env:
           COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }}
         run: |
-          pip install coveragepy-lcov
+          pip install click==8.1.3
+          pip install coverage==6.5.0
+          pip install coveragepy-lcov==0.1.2
           coveragepy-lcov --data_file_path coverage_results.cov --output_file_path lcov.txt
       - name: Publish to coveralls.io
         uses: coverallsapp/github-action@v1.1.2

doc/release/0.2.rst

@@ -23,6 +23,7 @@ Bug fixes
 #. Removed Barriers in temp directory changers and output cache to avoid deadlocks in MPI cases
 #. Fixed bug with database writing and tight coupling. (`PR#1005 https://github.com/terrapower/armi/pull/1005`)
 #. Fixed a bug where snapshot load would not respect the new cs["power"] setting.
+#. Froze the NumPy version to be <= 1.23.5 (`PR#1035 https://github.com/terrapower/armi/pull/1035`) to continue to support numpy jagged arrays within the Database interface.
 
 ARMI v0.2.5
 ===========

requirements-testing.txt

@@ -1,5 +1,5 @@
 --prefer-binary
-numpy>=1.21
+numpy>=1.21,<=1.23.5
 
 # docutils 0.17 introduced a bug that prevents bullets from rendering
 # see https://github.com/terrapower/armi/issues/274

requirements.txt

@@ -2,6 +2,6 @@
 --prefer-binary
 # see https://github.com/advisories/GHSA-6p56-wp2h-9hxr
 # This is included in requirements.txt because of a security alert numpy released
-numpy>=1.21
+numpy>=1.21,<=1.23.5
 
 -e .[memprof]

setup.py

@@ -60,7 +60,7 @@ def collectExtraFiles():
         "future",
         "h5py>=3.0",
         "matplotlib",
-        "numpy",
+        "numpy>=1.21,<=1.23.5",
         "ordered-set",
         "pillow",
         "pluggy",