Skip to content

chore(deps): bump gitpython to 3.1.57 - #126

Open
dustenhubbard wants to merge 1 commit into
mainfrom
chore/bump-gitpython-advisories
Open

chore(deps): bump gitpython to 3.1.57#126
dustenhubbard wants to merge 1 commit into
mainfrom
chore/bump-gitpython-advisories

Conversation

@dustenhubbard

@dustenhubbard dustenhubbard commented Jul 31, 2026

Copy link
Copy Markdown
Member

Bumps gitpython from 3.1.50 to 3.1.57 in requirements.txt and pyproject.toml, clearing the nine advisories on that pin (fixes land across 3.1.51 through 3.1.55; 3.1.57 is current and three of the nine are follow-up fixes for earlier entries in the series).

Nothing else moves: gitpython is pure Python with no declared dependencies and a >=3.7 floor. The only calls in the tree are git.Repo(), head.commit.hexsha, and active_branch.name in modules/constants/repo_info.py, and every advisory is in clone, remote, archive, diff, or config handling, so this is pin hygiene rather than a reachable fix.

Leaves vtk==9.3.1 alone deliberately. Its three CVEs are first fixed in 9.5.1, and bumping that pin on its own breaks the 3D scene: VPlotter.__init__ builds vedo.Text2D unconditionally and vtk 9.4+ raises TypeError: ... requires a vtkProperty2D. It needs a matching vedo bump plus three transform call sites, so it wants its own change. Happy to write that up separately.

Refs #112

`gitpython==3.1.50` is affected by nine published advisories, every one of
them a command-injection or argument-injection path. `3.1.57` clears all
nine. The last fix in the series landed in `3.1.55`; `3.1.57` is taken
rather than `3.1.55` because three of the nine were incomplete fixes for
earlier ones, and the later releases are where that pattern settled.

The bump moves nothing else. `gitpython` is pure Python, declares no
dependencies, and its floor is `>=3.7`. The only usage is
`PyReconstruct/modules/constants/repo_info.py`, which calls
`git.Repo(repo_dir)` and reads `head.commit.hexsha` and
`active_branch.name`. None of the nine advisories touch that surface, so
this is hygiene on the pin rather than a fix for reachable behavior.

Verified on Python 3.11 against the rest of the pinned set: install
resolves, `git.Repo()` and both attribute reads work unchanged.

Refs #112.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant