Added .zenodo.json file and updated jinja2 to 3.1.5 (security fix) #304
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.zenodo.json - Added this file to trigger automatic DOI generation and auto-population of fields every time a HEMCO release is issued at GitHub docs/requirements.txt - Bumped jinja2 to version 3.1.5 as suggested by GitHub Dependabot. This fixes a security issue. Jinja2 is used by ReadTheDocs. CHANGELOG.md - Updated accordingly
yantosca
added
no-diff-to-benchmark
lizziel
approved these changes
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
In this PR we have done the following:
.zenodo.jsonfile, which will auto-populate fields when a DOI is triggered by each HEMCO release.jinja2package (which is used by ReadTheDocs) to version 3.1.5 indocs/requirement.txt. This fixes a security issue identified by GitHub Dependabot.Expected changes
These are zero-diff updates and can be merged alongside another HEMCO PR. It can go either into 3.10.2 or 3.11.0, whichever is worked on first.