[Infra] Version Bump

[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 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 PR bumps the LiteLLM package version from 1.83.14 to 1.84.0 in pyproject.toml and regenerates uv.lock to reflect the new version. The lockfile also updates the exclude-newer timestamp to an epoch sentinel value (0001-01-01T00:00:00Z) to indicate that the active resolution constraint is now driven entirely by exclude-newer-span = "P3D", which is consistent with how newer versions of uv handle relative time spans.

Confidence Score: 5/5

Safe to merge — purely a version bump with no logic changes.

Only two files changed: a version string update in pyproject.toml and the corresponding uv.lock regeneration. No code logic, dependencies, or security-relevant paths are touched.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Version bumped from 1.83.14 to 1.84.0 in both [project] and [tool.commitizen] sections — straightforward and consistent.
uv.lock	litellm version updated to 1.84.0; exclude-newer timestamp zeroed out with backwards-compatibility comment while exclude-newer-span remains as the active constraint.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["pyproject.toml\nversion: 1.83.14 → 1.84.0"] --> B["uv.lock regenerated\nlitellm version updated\nexclude-newer → epoch sentinel"]
    B --> C["Active resolution constraint:\nexclude-newer-span = P3D"]

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!