Skip to content

Bump GitPython to 3.1.59 to fix security scan - #43

Merged
plebioda merged 1 commit into
masterfrom
fix-security-scan-3
Aug 10, 2026
Merged

Bump GitPython to 3.1.59 to fix security scan#43
plebioda merged 1 commit into
masterfrom
fix-security-scan-3

Conversation

@plebioda

Copy link
Copy Markdown
Collaborator

Summary

The scheduled Security Scan workflow failed because pip-audit found 5 known vulnerabilities in GitPython 3.1.57, all fixed in 3.1.58:

This bumps the pin to GitPython==3.1.59 (latest).

Testing

  • pip install -e . resolves cleanly with GitPython 3.1.59
  • pip-audit --progress-spinner off --skip-editable no longer reports gitpython vulnerabilities

🤖 Generated with Claude Code

pip-audit flagged 5 known vulnerabilities in GitPython 3.1.57
(GHSA-9rj7-rf2p-w77r, GHSA-4gmw-gg2m-w46p, GHSA-hh9p-6wh2-4mfc,
GHSA-wvpp-8hx9-p66j, GHSA-jm78-9fvv-mhgr), all fixed in 3.1.58.
Pin to the latest 3.1.59.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the project’s pinned GitPython dependency to address vulnerabilities reported by the scheduled security scan, keeping the runtime dependency set aligned with the repository’s existing “exact pin” approach.

Changes:

  • Bump GitPython from 3.1.57 to 3.1.59 in pyproject.toml.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@plebioda
plebioda merged commit 9d035b2 into master Aug 10, 2026
9 checks passed
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.

2 participants