Upgrade jinja2 to 2.10.1 #4737
Merged
Upgrade jinja2 to 2.10.1 #4737
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
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.
2.10.1 adds protection to
format_map. We don't use this, but Github is nagging.(We upgraded jinja2 only a few days ago but this wasn't sufficient to stop the nagging)
The changelog is purely fixes and new new features - nothing backwards incompatible. I've clicked around in the web interface and it all seems fine to me.
This version is compatible with our version of flask - it requires
Jinja2>=2.4Features:
Please [X] all the boxes above that apply