bump: litellm-proxy-extras 0.4.75, litellm-enterprise 0.1.46

[yuneng-berri]

Relevant issues

Linear ticket

Pre-Submission checklist

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

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

N/A; version-bump-only change. uv lock resolved cleanly with just the two packages updated

Resolved 415 packages
Updated litellm-enterprise v0.1.45 -> v0.1.46
Updated litellm-proxy-extras v0.4.74 -> v0.4.75

Type

🧹 Refactoring

Changes

litellm-proxy-extras and enterprise both diverged from main on litellm_internal_staging, so their published versions need a PATCH bump before the next main promotion. litellm-proxy-extras picked up schema.prisma plus two new migrations, and enterprise changed check_batch_cost.py and managed_files.py

This bumps litellm-proxy-extras 0.4.74 -> 0.4.75 and litellm-enterprise 0.1.45 -> 0.1.46 via commitizen, propagates the versions into the root pyproject.toml pins, and relocks uv.lock. No git tags were created; the bumps were applied files-only

[greptile-apps]

Greptile Summary

This is a patch-version-only bump for two internal packages (litellm-proxy-extras 0.4.74 → 0.4.75 and litellm-enterprise 0.1.45 → 0.1.46) that diverged from main on the litellm_internal_staging branch. The root pyproject.toml pin and uv.lock are updated accordingly.

• Version strings updated consistently via commitizen in both sub-package pyproject.toml files (both the [project] and [tool.commitizen] sections).
• Root pyproject.toml proxy extras pinned to the new versions; uv.lock regenerated cleanly, with the exclude-newer timestamp advancing from 2026-06-27 to 2026-06-30 as expected when uv lock is rerun at a later date.

Confidence Score: 5/5

Version-bump-only change touching only pyproject.toml files and the lockfile; no production logic altered.

All four changed files contain only version string updates and a lockfile regeneration. The package version fields are internally consistent across all files, and the uv.lock exclude-newer timestamp advance is the expected side-effect of relocking at a later date.

No files require special attention.

Important Files Changed

Filename	Overview
enterprise/pyproject.toml	Version bumped from 0.1.45 to 0.1.46 via commitizen; both the [project] and [tool.commitizen] version fields updated consistently.
litellm-proxy-extras/pyproject.toml	Version bumped from 0.4.74 to 0.4.75 via commitizen; both the [project] and [tool.commitizen] version fields updated consistently.
pyproject.toml	Pinned dependencies in the [proxy] extras updated to reflect the new versions: litellm-proxy-extras==0.4.75 and litellm-enterprise==0.1.46.
uv.lock	Lockfile regenerated: both package versions updated, and the exclude-newer timestamp advanced from 2026-06-27 to 2026-06-30 as a natural result of running uv lock at a later date.

_{Reviews (1): Last reviewed commit: "bump: litellm-proxy-extras 0.4.74 -> 0.4..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!