Updated packaging and jinja2 pinned versions #188
Merged
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.
This is a small PR to update two dependencies,
packagingandjinja2.packaging: Updated pinned version from
^22.0->>= 22.0, < 24.0. I'm in the process of updating pinned versions of dependencies in my own library SigmAIQ, one of which islangchain(more specifically,langchain-core). The most recent minor version oflangchain-corerequirespackaging = ^23.2. This change solves the dependency conflict, and doesn't appear to have any adverse affects for pySigma after updating and running all the tests.jinja2: Updated pinned version from
^3.1.2->^3.1.3. All jinja2 versions prior to 3.1.3 are vulnerable to CVE-2024-22195