Bump gitpython past seven known vulnerabilities - #24
Merged
Conversation
`preen check --strict` had one gating finding here: gitpython 3.1.55 carries GHSA-3f7w-8rr8-f37f, GHSA-p538-c434-8v24, GHSA-9rj7-rf2p-w77r, GHSA-4gmw-gg2m-w46p, GHSA-hh9p-6wh2-4mfc, GHSA-wvpp-8hx9-p66j and GHSA-jm78-9fvv-mhgr, with fixes from 3.1.56. The lock now resolves 3.1.59. `uv lock --upgrade-package gitpython` also moved the py-canon git dependency, because it tracks the moving `v1` tag and that tag has advanced. That is a lock refresh doing its job rather than a second change smuggled in here. preen --strict now exits 0. ruff, pyright and 102 tests pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
preen check --stricthad exactly one gating finding on this repo:uv lock --upgrade-package gitpythonresolves 3.1.59. preen --strict now exits 0.One thing to know about the diff
The lock refresh also moved the
py-canongit dependency, because it tracks the movingv1tag and that tag has advanced. That is the lock doing its job, not a second change smuggled in — it is 4 lines of the 8-line diff.Verification
preen check --strictexit 0 ·ruff checkclean ·pyright0 errors · 102 tests pass.Part of a fleet-wide conformance pass from gojiplus/py-canon.