chore: bump litellm-proxy-extras 0.4.75 -> 0.4.76

[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 received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

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

Not applicable. A version bump has no runtime behavior to demonstrate; the change is limited to package version strings and the refreshed lock

Type

🚄 Infrastructure

Changes

Routine pre-release version bump ahead of promoting litellm_internal_staging into main for this week's release candidate. The litellm-proxy-extras folder changed since the last release while its version still matched main, so it gets a PATCH bump from 0.4.75 to 0.4.76. That updates litellm-proxy-extras/pyproject.toml, the litellm-proxy-extras== pin in the root pyproject.toml, and uv.lock

enterprise is unchanged from main, and the root litellm package stays on the 1.93.0 line (this promotion cuts that line's rc rather than opening a new minor line), so neither is bumped. The only extra line in the uv.lock diff is the rolling exclude-newer window moving forward, which is expected; uv lock reported litellm-proxy-extras as the sole updated package

[greptile-apps]

Greptile Summary

Routine PATCH version bump for litellm-proxy-extras (0.4.75 → 0.4.76) in preparation for promoting litellm_internal_staging to main. The root package's proxy extras pin and uv.lock are updated in lockstep; no logic or behaviour changes are included.

• litellm-proxy-extras/pyproject.toml — version string updated in both [project] and [tool.commitizen] sections.
• pyproject.toml — proxy extras pin advanced to ==0.4.76.
• uv.lock — lock entry updated to 0.4.76 and exclude-newer window rolled forward by ~6 hours, as expected from re-running uv lock.

Confidence Score: 5/5

Safe to merge — all three changed files are version strings and a lock-file snapshot with no logic changes.

Every change is a mechanical version-string update: the sub-package pyproject.toml, the root pyproject.toml pin, and the lock file. No code paths, dependencies, or behaviours are altered, and the uv.lock diff shows only litellm-proxy-extras as the updated package with a minor exclude-newer window roll.

No files require special attention.

Important Files Changed

Filename	Overview
litellm-proxy-extras/pyproject.toml	PATCH version bump from 0.4.75 to 0.4.76 in both the [project] version field and the [tool.commitizen] version field — no other changes.
pyproject.toml	Root package's proxy extras pin updated from litellm-proxy-extras==0.4.75 to ==0.4.76 to match the sub-package bump.
uv.lock	Lock file entry for litellm-proxy-extras updated to 0.4.76 and exclude-newer window advanced by ~6 hours; only one package reported as updated by uv lock.

_{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_/weekly-rc-release-dbe6a9 (af8c6e5) with litellm_internal_staging (e7f4144)}