-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update jinja2 per CVE-2024-34064 #10030
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Future work: on the top of requirements.txt
I read:
# This file is autogenerated by pip-compile with Python 3.11
# by the following command:
I wonder whether we can axe it from version control so we have just one file where to bump dependencies.
It'll take a little work since currently the RTD run doesn't depend on anything else, but we'll need to make sure it runs after the file has been generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bless your heart! 🙏
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
So do we want to backport this? Also, given we just got another one, I'm wondering if #10031 should be backported after all. |
@mergify backport 3.12 |
✅ Backports have been created
|
update jinja2 per CVE-2024-34064 (backport #10030)
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
* generate doc/requirements.txt As suggested in #10030 (review) * generate doc/requirements.txt As suggested in #10030 (review)
* generate doc/requirements.txt As suggested in #10030 (review) * generate doc/requirements.txt As suggested in #10030 (review) (cherry picked from commit 2658ac6)
* generate doc/requirements.txt As suggested in #10030 (review) * generate doc/requirements.txt As suggested in #10030 (review) (cherry picked from commit 2658ac6)
* generate doc/requirements.txt As suggested in haskell#10030 (review) * generate doc/requirements.txt As suggested in haskell#10030 (review)
* generate doc/requirements.txt As suggested in haskell#10030 (review) * generate doc/requirements.txt As suggested in haskell#10030 (review)
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: