MAINT: make sure the next env covers new CVEs #306
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
|
Well, this makes next incr pass, which is something I guess. The current env failure reflects the reality that the current env has some known vulnerabilities. |
tangkong
reviewed
Nov 13, 2023
| @@ -11,6 +11,7 @@ | |||
| ACK_LIST = { | |||
| "GHSA-29gw-9793-fvw7": "Windows-only", | |||
| "PYSEC-2023-163": "Only affects langchain users", | |||
| "PYSEC-2021-878": "Fixed in 1.2.2, mistakenly attached to 1.5.3", | |||
There was a problem hiding this comment.
more info on this for my own education
I've recently started to hear about people submitting CVE's maliciously, a fascinating world software is
tangkong
approved these changes
Nov 13, 2023
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.
I think I'd rather do this as we go instead of all at once at env tag time