[Infra] bump versions

[yuneng-berri]

Relevant issues

Pre-Submission checklist

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

• I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• 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).

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Screenshots / Proof of Fix

Type

🚄 Infrastructure

Changes

[greptile-apps]

Greptile Summary

This is a routine infrastructure version bump: litellm is incremented from 1.83.11 → 1.83.12 and litellm-proxy-extras from 0.4.67 → 0.4.68. All three files (pyproject.toml, litellm-proxy-extras/pyproject.toml, and uv.lock) are updated consistently, including the exclude-newer resolver timestamp in the lock file.

Confidence Score: 5/5

Safe to merge — pure version bump with no logic changes.

All changes are mechanical version number increments consistent across every relevant file. No code logic, security, or custom rules are affected.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Main litellm version bumped from 1.83.11 → 1.83.12, and litellm-proxy-extras dependency updated from 0.4.67 → 0.4.68; both commitizen and project version fields updated consistently.
litellm-proxy-extras/pyproject.toml	litellm-proxy-extras version bumped from 0.4.67 → 0.4.68 in both [project] and [tool.commitizen] sections.
uv.lock	Lock file updated to reflect new litellm (1.83.12) and litellm-proxy-extras (0.4.68) versions; exclude-newer timestamp advanced by ~1 day to 2026-04-20.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["pyproject.toml\nlitellm 1.83.11 → 1.83.12\nlitellm-proxy-extras==0.4.67 → 0.4.68"] -->|depends on| B["litellm-proxy-extras/pyproject.toml\n0.4.67 → 0.4.68"]
    A -->|lock file regenerated| C["uv.lock\nexclude-newer: 2026-04-19 → 2026-04-20\nlitellm 1.83.12\nlitellm-proxy-extras 0.4.68"]
    B --> C

Loading

_{Reviews (1): Last reviewed commit: "uv lock" | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!