Skip to content

[Infra] Bump version - #26209

Merged
yuneng-berri merged 2 commits into
litellm_internal_stagingfrom
yj_bump_apr21_2
Apr 22, 2026
Merged

[Infra] Bump version#26209
yuneng-berri merged 2 commits into
litellm_internal_stagingfrom
yj_bump_apr21_2

Conversation

@yuneng-berri

Copy link
Copy Markdown
Contributor

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-apps Bot commented Apr 22, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR bumps the LiteLLM package version from 1.83.10 to 1.83.11 in pyproject.toml and the uv.lock lockfile, and advances the exclude-newer resolver timestamp in uv.lock by ~3 days.

Confidence Score: 5/5

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

Only two files changed; both changes are mechanical version string updates and a lock-file timestamp refresh. No custom rules are violated and there are no logic, security, or correctness concerns.

No files require special attention.

Important Files Changed

Filename Overview
pyproject.toml Version bumped from 1.83.10 to 1.83.11 in both [project] and [tool.commitizen] sections
uv.lock Lock file updated: litellm version bumped to 1.83.11 and exclude-newer timestamp advanced to 2026-04-19

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pyproject.toml\nversion: 1.83.10] -->|bump| B[pyproject.toml\nversion: 1.83.11]
    C[uv.lock\nversion: 1.83.10\nexclude-newer: 2026-04-16] -->|refresh| D[uv.lock\nversion: 1.83.11\nexclude-newer: 2026-04-19]
Loading

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

@codecov

codecov Bot commented Apr 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@yuneng-berri
yuneng-berri enabled auto-merge April 22, 2026 01:27
@yuneng-berri
yuneng-berri merged commit e3ed136 into litellm_internal_staging Apr 22, 2026
42 checks passed
@yuneng-berri
yuneng-berri deleted the yj_bump_apr21_2 branch April 22, 2026 01:29
fzowl pushed a commit to fzowl/litellm that referenced this pull request Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants