fix: update vulnerable Python dependencies - #1
Draft
Alekseylekontsev wants to merge 9 commits into
Draft
Conversation
This file contains hidden or 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.
What changed
uv.lockSECURITY_DEPENDENCY_REPORT.mdWhy
The supplied audit reported 47 findings, including a critical ChromaDB code-injection advisory and high-severity issues in cryptography, MCP, Starlette, and python-multipart. ChromaDB is no longer in the synchronized upstream dependency graph; the remaining affected packages are upgraded to patched versions.
Validation
Windows status
This machine has no installed WSL Linux distribution. Native-Windows dependency installation works for core/all/dev/messaging/MCP/web/Google/Teams profiles, but the complete suite cannot be collected because three tests assume POSIX facilities (
termios,/tmp, andwhich). Since upstream Hermes documents WSL2 as the supported Windows path, full runtime compatibility remains unverified until the suite is rerun inside WSL2. Details are recorded in the report.