Skip to content

[Infra] Bump Version to 1.83.0#24840

Merged
ishaan-berri merged 2 commits intomainfrom
litellm_version_bump_1_83_0
Mar 31, 2026
Merged

[Infra] Bump Version to 1.83.0#24840
ishaan-berri merged 2 commits intomainfrom
litellm_version_bump_1_83_0

Conversation

@yuneng-berri
Copy link
Copy Markdown
Collaborator

Summary

  • Bump litellm version from 1.82.6 to 1.83.0
  • Bump litellm-proxy-extras dependency from ^0.4.61 to ^0.4.62

Changes

Version bump only — no code changes.

Type

🚄 Infrastructure

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 31, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Mar 31, 2026 5:01am

Request Review

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 31, 2026

Greptile Summary

This PR bumps the litellm package version from 1.82.6 to 1.83.0 and updates the optional litellm-proxy-extras dependency from ^0.4.61 to ^0.4.62. The poetry.lock file is updated accordingly with new file hashes and a refreshed content-hash.

  • pyproject.toml: Version string updated in [tool.poetry], litellm-proxy-extras constraint updated, and [tool.commitizen] version updated — all consistent.
  • poetry.lock: litellm-proxy-extras entry updated to 0.4.62 with correct wheel and sdist hashes; content-hash regenerated.
  • No code, logic, test, or configuration changes are present.

Confidence Score: 5/5

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

The PR contains only version string and dependency version updates. The lock file hashes are consistent with the declared versions. No tests, logic, or configurations are modified, so there is no regression risk.

No files require special attention.

Important Files Changed

Filename Overview
pyproject.toml Version bumped from 1.82.6 to 1.83.0 and litellm-proxy-extras dependency updated from ^0.4.61 to ^0.4.62; no other changes.
poetry.lock Lock file updated to reflect new litellm-proxy-extras 0.4.62 hashes and refreshed content-hash; consistent with pyproject.toml changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["pyproject.toml\nversion: 1.82.6 → 1.83.0"] --> C["poetry.lock\ncontent-hash updated"]
    B["litellm-proxy-extras\n0.4.61 → 0.4.62"] --> C
    C --> D["Package Release\nlitellm 1.83.0"]
Loading

Reviews (2): Last reviewed commit: "update poetry.lock for version bump" | Re-trigger Greptile

@codspeed-hq
Copy link
Copy Markdown
Contributor

codspeed-hq bot commented Mar 31, 2026

Merging this PR will not alter performance

✅ 16 untouched benchmarks


Comparing litellm_version_bump_1_83_0 (51830de) with main (0ea0546)

Open in CodSpeed

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@yuneng-berri yuneng-berri temporarily deployed to integration-redis-postgres March 31, 2026 04:58 — with GitHub Actions Inactive
@yuneng-berri yuneng-berri temporarily deployed to integration-postgres March 31, 2026 04:58 — with GitHub Actions Inactive
@yuneng-berri yuneng-berri temporarily deployed to integration-postgres March 31, 2026 04:58 — with GitHub Actions Inactive
@yuneng-berri yuneng-berri temporarily deployed to integration-postgres March 31, 2026 04:58 — with GitHub Actions Inactive
@yuneng-berri yuneng-berri temporarily deployed to integration-postgres March 31, 2026 04:58 — with GitHub Actions Inactive
@ishaan-berri ishaan-berri merged commit f0518c1 into main Mar 31, 2026
57 of 104 checks passed
@ishaan-berri ishaan-berri deleted the litellm_version_bump_1_83_0 branch March 31, 2026 05:00
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.

3 participants