Repository navigation
Bump GitPython to 3.2.1 and certifi to 2026.10.19 - #372
Conversation
Dependabot alerts #48, #50-#54 (GitPython <= 3.2.0) and #49 (certifi < 2026.10.18, emSign roots with compromised intermediates). The GitPython floor in pyproject.toml moves to >=3.2.1, which fixes all six. claude-code-log only calls Repo(cwd, search_parent_directories=True) to find the git root, none of the affected APIs (submodules, Remote.pull, Head.checkout, command wrappers, actor parsing), so the exposure was low; the floor is what users install against. certifi only arrives through dev/docs tooling (requests, via mkdocs-material and pytest-base-url), so only the lockfile changes. 2026.10.19 is the newest release at least two weeks old. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Dependabot alerts #48, #50-#54 (GitPython <= 3.2.0) and #49 (certifi
< 2026.10.18, emSign roots with compromised intermediates).
The GitPython floor in pyproject.toml moves to >=3.2.1, which fixes all
six. claude-code-log only calls Repo(cwd, search_parent_directories=True)
to find the git root, none of the affected APIs (submodules,
Remote.pull, Head.checkout, command wrappers, actor parsing), so the
exposure was low; the floor is what users install against.
certifi only arrives through dev/docs tooling (requests, via
mkdocs-material and pytest-base-url), so only the lockfile changes.
2026.10.19 is the newest release at least two weeks old.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Summary by CodeRabbit