update release checklist

[twicki]

Description

With the move to pinned releases of NDSL used in pyFV3 (see here) we need to add to the release checklist to ensure we keep up to date on those as well.

How has this been tested?

no testing required, docs only change

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. add new modules to docs/docstrings/)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• New check tests, if applicable, are included

[romanc]

Maybe let's also add the pySHiELD repo. pace is already there and I'm not sure how verbose we want to be about pyMoist, especially since we don't have anything merged down to mainline GEOS.

[twicki]

pyShield currently points to develop: https://github.com/NOAA-GFDL/pySHiELD/blob/1ed483cf854244fd02e59d5817d9332610042178/pyproject.toml#L43 . Should we move that to be tagged as well?

[fmalatino]

pyShield currently points to develop: https://github.com/NOAA-GFDL/pySHiELD/blob/1ed483cf854244fd02e59d5817d9332610042178/pyproject.toml#L43 . Should we move that to be tagged as well?

I think in general we should always move to the current release for each of the dependencies, but I am open to other opinions.

[romanc]

+1 for using released versions unless we have compelling reasons, e.g. when propagating breaking changes.

[twicki]

update to the checklist done.

PR in SHiELD open to pin as well: NOAA-GFDL/pySHiELD#94