You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore: bump litellm-proxy-extras to 0.4.107 and litellm-enterprise to 0.1.75 - #45291
uv lock --check; echo "exit=$?" with the box uv 0.12.23, and the same check under uvx uv@0.12.10 and uvx uv@0.11.7 (the Dockerfile UV_IMAGE pin) also exits 0
The dots are escaped here because the unescaped pattern 0.4.106|0.1.74 also matches 8 sha256 wheel hashes in uv.lock that are on main unchanged (for example 001f74 in the fastuuid hash on line 1968). With escaped dots no version string is left
[High risk] Bumps internal package versions in dependency lockfile.
This PR appears safe to merge; the version bumps stay consistent across all four changed files
What we checked:
Local package versions agree: Both lock entries match the package manifests and root pins. These packages use local editable sources, so no wheel URLs or hashes need changing
Summary
Bumps litellm-proxy-extras to 0.4.107 and litellm-enterprise to 0.1.75. Both package manifests, their commitizen versions, the root dependency pins, and uv.lock agree
No actionable issues found. The changes only update versions; dependency declarations and package sources stay unchanged
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
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.
TLDR
Problem this solves:
How it solves it:
[project]and[tool.commitizen]pyproject.tomlpins and the twouv.lockversion lines by hand, no relockScreenshots / Proof of Fix
After (b7d372a)
git diff --stat origin/main...HEADuv lock --check; echo "exit=$?"with the box uv 0.12.23, and the same check underuvx uv@0.12.10anduvx uv@0.11.7(the DockerfileUV_IMAGEpin) also exits 0git grep -nE '0\.4\.106|0\.1\.74' -- pyproject.toml litellm-proxy-extras/pyproject.toml enterprise/pyproject.toml uv.lock; echo "exit=$?"The dots are escaped here because the unescaped pattern
0.4.106|0.1.74also matches 8 sha256 wheel hashes inuv.lockthat are on main unchanged (for example001f74in the fastuuid hash on line 1968). With escaped dots no version string is leftType
🚄 Infrastructure
Link to Devin session: https://app.devin.ai/sessions/8c31e8c73ab944ba97681ffed10a025e
Open in Devin Desktop: https://app.devin.ai/desktop/session/8c31e8c73ab944ba97681ffed10a025e?variant=devin