chore: bump litellm-enterprise 0.1.63 -> 0.1.64, litellm-proxy-extras 0.4.92 -> 0.4.93

[yuneng-berri]

TLDR

Problem this solves:

• enterprise/ and litellm-proxy-extras/ changed on staging since the last release
• both still carry the version main ships, so the next publish would be stale

How it solves it:

• litellm-enterprise 0.1.63 -> 0.1.64 (PATCH)
• litellm-proxy-extras 0.4.92 -> 0.4.93 (PATCH)
• root pyproject pins updated to match, uv.lock re-resolved in one pass
• litellm stays at 1.101.0: the line only has v1.101.0-dev.1, no rc yet

User Flow

Not applicable. This changes nothing at runtime, only the version each package publishes as

Relevant issues

None

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests (not applicable, version-only change)
• The handful of test files covering my change pass locally (not applicable, version-only change)
• 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

Screenshots / Proof of Fix

There is no meaningful proof for a version bump. uv lock reported only the two editable packages as updated and uv lock --check passes on the tip

Type

🚄 Infrastructure

Caveats (if any)

Low

• uv.lock's exclude-newer line goes from the placeholder back to an absolute timestamp
  • the placeholder came in with test(harness): add OCR parity with migration strategy runners #38765 from a newer uv; CI and this run use the pinned uv 0.10.9
  • no third-party dependency version moved

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_/release-version-bump-be1c60 (ba9bb75) with litellm_internal_staging (7d6781f)}

[greptile-apps]

Greptile Summary

This PR prepares the next patch releases of the enterprise and proxy-extras packages.

• Bumps litellm-enterprise from 0.1.63 to 0.1.64.
• Bumps litellm-proxy-extras from 0.4.92 to 0.4.93.
• Synchronizes the root proxy-extra pins and editable workspace lockfile entries.
• Re-serializes the lockfile’s rolling three-day dependency cutoff.

Confidence Score: 5/5

The PR appears safe to merge because the package versions and dependency pins remain synchronized and no actionable failure was identified.

The changes are coordinated metadata updates, and the lockfile retains the same effective relative dependency cutoff while matching both workspace package versions.

Important Files Changed

Filename	Overview
enterprise/pyproject.toml	Consistently updates the enterprise project and commitizen versions to 0.1.64.
litellm-proxy-extras/pyproject.toml	Consistently updates the proxy-extras project and commitizen versions to 0.4.93.
pyproject.toml	Updates both exact proxy-extra package pins to match their new project versions.
uv.lock	Synchronizes both editable workspace package versions and validly serializes the existing rolling dependency cutoff.

_{Reviews (1): Last reviewed commit: "bump: litellm-enterprise 0.1.63 -> 0.1.6..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!