chore: bump litellm 1.93.0 -> 1.94.0, litellm-enterprise 0.1.49 -> 0.1.50, litellm-proxy-extras 0.4.76 -> 0.4.77

[yuneng-berri]

Relevant issues

None — routine pre-release version bumps ahead of promoting litellm_internal_staging into main.

Pre-Submission checklist

• I have added meaningful tests — N/A: version-only bump, no code change
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• Greptile Confidence Score — will follow once Greptile auto-reviews

Screenshots / Proof of Fix

N/A. This is a version-only bump (pyproject.toml versions + uv.lock); there is no runtime behavior to demonstrate.

Type

🚄 Infrastructure

Changes

Pre-release version bumps required before promoting litellm_internal_staging into main, produced by the release-version-bump procedure:

• litellm-enterprise: 0.1.49 -> 0.1.50 (PATCH — enterprise/ changed since last release)
• litellm-proxy-extras: 0.4.76 -> 0.4.77 (PATCH — litellm-proxy-extras/ changed since last release)
• litellm (root): 1.93.0 -> 1.94.0 (MINOR — the 1.93.0 line already shipped an rc (v1.93.0-rc.1), so this promotion opens the 1.94.0 line)

Plus the corresponding uv.lock refresh: only the three editable packages move, and the [options] exclude-newer timestamp advances per the rolling P3D window. No third-party dependency versions changed.

Final Attestation

• N/A — version-only bump, no tests changed.

[greptile-apps]

Greptile Summary

Routine pre-release version bump across three packages ahead of promoting litellm_internal_staging to main. No code logic was changed — only version strings and the uv.lock snapshot were updated.

• litellm root: 1.93.0 → 1.94.0 (opens the 1.94.0 line since 1.93.0 already shipped an RC); pinned proxy extra constraints in [project.optional-dependencies] updated to match.
• litellm-enterprise: 0.1.49 → 0.1.50; litellm-proxy-extras: 0.4.76 → 0.4.77.
• uv.lock refreshed: all three editable package entries bumped, exclude-newer timestamp advanced by ~1 day; no third-party dependency versions changed.

Confidence Score: 5/5

Version-only bump with no code changes; safe to merge.

The entire diff is version strings and a lock file timestamp refresh. No logic, tests, migrations, or dependencies were modified — the only risk is a typo in a version number, and all four changed files are internally consistent (the pinned constraints in pyproject.toml match the new sub-package versions, and uv.lock reflects all three bumps).

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Root package version bumped 1.93.0 → 1.94.0; pinned proxy extras updated to match new sub-package versions
enterprise/pyproject.toml	litellm-enterprise version bumped 0.1.49 → 0.1.50; commitizen version_files updated accordingly
litellm-proxy-extras/pyproject.toml	litellm-proxy-extras version bumped 0.4.76 → 0.4.77; commitizen version_files updated accordingly
uv.lock	Lock file refreshed: all three editable package versions updated and exclude-newer timestamp advanced by ~1 day; no third-party dependency versions changed

_{Reviews (1): Last reviewed commit: "Merge remote-tracking branch 'origin/lit..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_release_version_bump_1_94_0 (27fa50b) with litellm_internal_staging (41b0300)}