Repository navigation
Bump vulnerable dependencies in uv.lock - #345
Merged
Merged
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.
Bumps only the locked packages that pip-audit flagged (certifi for the emSign root CA, pyjwt, aiohttp, cryptography, urllib3, requests, sqlparse and others), using
uv lock --upgrade-package. pyproject ranges are unchanged.oauthlib stays at 3.3.1 because databricks-sql-connector caps it below 4, and paramiko has no fixed release yet.
Locally the unit suite passes (2143 passed) apart from test_detect_strategy_pip_user_fallback, which fails on main too in this environment. The SQLite tests also pass.
Note: This only updates the versions locked in
uv.lock. sqlit's releases don't install from the lockfile; pip, AUR and Nix resolve dependencies themselves. So these locked versions only affected local development and CI, not users.