We did not capture this in the change log for the release, but v3.14.0 does not work with Python 3.7, i.e. we dropped Python 3.7 support for that (latest) release, because we upgraded the numpy version requirement from numpy>=1.15 at our v3.13.1 (the previous release to v3.14.0) to numpy>=1.22 (for quick evidence, compare https://github.com/NCAS-CMS/cf-python/blob/v3.14.0/requirements.txt#L3 to https://github.com/NCAS-CMS/cf-python/blob/3.13.1/requirements.txt#L3), and Numpy's 1.22 dropped support for 3.7. (The numpy dependency update was also not captured in the change log.)

Hence the erroring on setup steps of the 3.7 jobs in the CI/Actions workflows, where the jobs for other Python versions pass (or fail for legimate test method issue reasons).

Approach

Because of this, we should indicate for the next release that Python 3.7 support is dropped, but really this began at the prevoous release, version v3.14.0. Should we retrospectively add to the change log entry at v3.14.0 instead to correctly indicate when Python 3.7 support was truly lost, or is it bad practice to edit that entry well after the time of release?