chore: bump litellm-proxy-extras 0.4.78 -> 0.4.79

[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

There is no runtime behavior to prove for a version bump; the diff is the change. uv lock reported only litellm-proxy-extras as updated and uv lock --check passes with the CI-pinned uv 0.10.9

Type

🚄 Infrastructure

Changes

litellm-proxy-extras changed on litellm_internal_staging since the last promotion to main while still carrying main's version, so it gets a PATCH bump before the next release: 0.4.78 -> 0.4.79, with the matching pin updated in the root pyproject.toml. enterprise/ is unchanged since the last promotion and the root litellm package stays at 1.94.0 since that line has not shipped an rc or stable yet

uv.lock is refreshed against the bumped version; the lock diff is the one version entry plus the rolling exclude-newer timestamp. No third-party dependency versions changed

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

[greptile-apps]

Greptile Summary

This PR bumps the litellm-proxy-extras sub-package from 0.4.78 to 0.4.79 — a patch-level version increment — and updates the corresponding pin in the root pyproject.toml and refreshes uv.lock.

• litellm-proxy-extras/pyproject.toml: version field updated in both [project] and [tool.commitizen] sections.
• pyproject.toml: exact pin changed from ==0.4.78 to ==0.4.79 under the proxy extras group.
• uv.lock: only the litellm-proxy-extras version entry and the rolling exclude-newer timestamp changed; no third-party dependency versions are affected.

Confidence Score: 5/5

This is a minimal patch-version bump of an internal sub-package with no functional code changes; it is safe to merge.

The change consists entirely of version string updates across three files. No logic, configuration values, or third-party dependencies were modified — only the litellm-proxy-extras version number and the lock file's rolling timestamp changed.

No files require special attention.

Important Files Changed

Filename	Overview
litellm-proxy-extras/pyproject.toml	Version bumped from 0.4.78 to 0.4.79 in both [project] and [tool.commitizen] sections — straightforward patch bump, no other changes.
pyproject.toml	Pin for litellm-proxy-extras updated from ==0.4.78 to ==0.4.79 to match the bumped sub-package version.
uv.lock	Lock file refreshed: litellm-proxy-extras version entry updated to 0.4.79 and exclude-newer timestamp rolled forward to 2026-07-15; no third-party dependency versions changed.

_{Reviews (1): Last reviewed commit: "bump: litellm-proxy-extras 0.4.78 -> 0.4..." | 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-42c5e5 (4fe78ff) with litellm_internal_staging (e238e89)¹}

Footnotes

1. No successful run was found on litellm_internal_staging (567ebcb) during the generation of this report, so e238e89 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩