NEP29 and NumPy v2 pins

[trexfeathers]

🚀 Pull Request

Description

• NEP29
  • 2024-06-22: NumPy >=1.24
  • 0289e56
• NumPy v2
  • Demo Numpy v2 #6035 has proven that it will be a medium/large task to get all our tests supporting NumPy v2
  • We expect to have some slots to work on this for Iris v3.11 - 🐓 v3.11.x #5571
  • So we need a pin in the meantime, and I expect also a patch release

The lock files already fit between these two pins so I have not refreshed those.

---

Consult Iris pull request check list

---

Add any of the below labels to trigger actions on this PR:

• benchmark_this Request that this pull request be benchmarked to check if it introduces performance shifts

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.77%. Comparing base (d0801aa) to head (02fa42b).
Report is 61 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6039   +/-   ##
=======================================
  Coverage   89.77%   89.77%           
=======================================
  Files          90       90           
  Lines       22984    22984           
  Branches     5031     5031           
=======================================
  Hits        20634    20634           
  Misses       1619     1619           
  Partials      731      731           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[trexfeathers]

As well as getting the v2 pin onto main, which will set us up correctly for future testing then future releasing, note that I am also intending to cut a 3.9.0post0 release. Once this PR is merged, I will therefore be cherry-picking the squash commit onto the v3.9.x release branch.

[bjlittle]

As well as getting the v2 pin onto main, which will set us up correctly for future testing then future releasing, note that I am also intending to cut a 3.9.0post0 release. Once this PR is merged, I will therefore be cherry-picking the squash commit onto the v3.9.x release branch.

Yup, good move.

Remember to update the community on #5850 with our intentions 👍

[trexfeathers]

Thanks @bjlittle!

[trexfeathers]

As well as getting the v2 pin onto main, which will set us up correctly for future testing then future releasing, note that I am also intending to cut a 3.9.0post0 release. Once this PR is merged, I will therefore be cherry-picking the squash commit onto the v3.9.x release branch.

Yup, good move.

Remember to update the community on #5850 with our intentions 👍

I've basically run out of time before we cut the next release candidate anyway (see 3.10) - I'm unavailable to work on this next week. Based on lack of user feedback so far the impact is limited. Discussed with @SciTools/peloton this morning and this seemed acceptable to those present.