Skip to content

chore(deps): bump gitpython to 3.1.61 in uv.lock - #39584

Closed
yuneng-berri wants to merge 1 commit into
litellm_internal_stagingfrom
litellm_/gitpython-security-update-a83f95
Closed

yuneng-berri wants to merge 1 commit into
litellm_internal_stagingfrom
litellm_/gitpython-security-update-a83f95

Conversation

@yuneng-berri

Copy link
Copy Markdown
Contributor

TLDR

Problem this solves:

  • Locked gitpython 3.1.58 is three patch releases behind
  • Newer releases are out and stable

How it solves it:

  • Lock-only bump of gitpython to 3.1.61
  • No pyproject constraint touched; nothing else re-resolved

User Flow

Not user-facing. gitpython is a transitive test/dev dependency pulled in by mlflow-skinny, which asks for gitpython<4,>=3.1.9. Nothing in the proxy or SDK request path changes, so there is no before/after flow for an end user to walk

Relevant issues

Linear ticket

Pre-Submission checklist

  • I have added meaningful tests
  • The handful of test files covering my change pass locally, e.g. uv run pytest tests/test_litellm/<your_test_file>.py -v
  • My PR passes all required CI/CD checks (e.g., lint, schema.d.ts sync check, etc.)
  • My PR's scope is as isolated as possible; it only solves 1 specific problem
  • I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review

There are no tests for a lock-only dependency refresh. CI resolving and installing the lock is the check that matters here

Screenshots / Proof of Fix

Type

🚄 Infrastructure

Caveats (if any)

Low

  • 3.1.61 released 2026-08-28, past the 3 day cooldown

Lock-only refresh of the transitive gitpython pin (pulled in by
mlflow-skinny, which asks for gitpython<4,>=3.1.9). No pyproject
constraint change and no other package moved in the resolution.
@yuneng-berri
yuneng-berri requested a review from a team September 3, 2026 17:01
@greptile-apps

greptile-apps Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

No reviewable files after applying ignore patterns.

@codspeed

codspeed Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 31 untouched benchmarks


Comparing litellm_/gitpython-security-update-a83f95 (fc8f50c) with litellm_internal_staging (4990f06)1

Open in CodSpeed

Footnotes

  1. No successful run was found on litellm_internal_staging (342e447) during the generation of this report, so 4990f06 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

@codecov

codecov Bot commented Sep 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@yuneng-berri

Copy link
Copy Markdown
Contributor Author

Closing as redundant. Staging already bumped gitpython to 3.1.61 in #38765, so this branch has no net change against it.

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.

3 participants