Update package versions used in the GCPy environment; Also update GitHub actions to avoid deprecation warnings #329
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Name and Institution (Required)
Name: Bob Yantosca
Institution: Harvard + GCST
Describe the update
This is the companion PR to issues #326 and #328. These issues reported that GCPy installation from the Python Package Index (PyPi) failed due to the
xesmf==0.5.1
package having been de-listed. We have made the following updates:docs/environment_files/gcpy_environment.yml
anddocs/environment_files/gcpy_requirements.txt
to use the following package versions:python==3.12.0
xesmf==0.8.5
esmf==8.6.1
esmpy==8.6.1
docs/environment_files/read_the_docs_requirements.yml
anddocs/environment_files/read_the_docs_requirements.txt
to use the following package versions:jinja2==3.1.4
, this fixes a security issue raised by Dependabotcheckout@v4
CodeQL@v3
publish-python@v5
Expected changes
This will be a zero-diff update. I have tested the 1-year benchmark scripts using a new Mamba environment with the updated package versions and all plots/tables were generated properly.
Related Github Issue