Skip to content

bump litellm-enterprise to 0.1.36 - #25164

Merged
ishaan-berri merged 3 commits into
mainfrom
enterprise-v36
Apr 5, 2026
Merged

bump litellm-enterprise to 0.1.36#25164
ishaan-berri merged 3 commits into
mainfrom
enterprise-v36

Conversation

@ishaan-berri

Copy link
Copy Markdown
Contributor

Relevant issues / links

Bumps litellm-enterprise package version to keep in sync with published releases.

Pre-Submission checklist

  • Version bumped across all three files

Type

  • Bug fix

Changes

Bumps litellm-enterprise from 0.1.350.1.36 across:

  • enterprise/pyproject.toml
  • pyproject.toml
  • requirements.txt

@vercel

vercel Bot commented Apr 5, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Apr 5, 2026 0:14am

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

greptile-apps Bot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR bumps the litellm-enterprise package version from 0.1.35 to 0.1.36 across all three relevant package/dependency files to keep the enterprise package in sync with its published release.

  • enterprise/pyproject.toml: Updates both the [tool.poetry] version and [tool.commitizen] version fields to 0.1.36
  • pyproject.toml: Updates the optional litellm-enterprise dependency declaration to 0.1.36
  • requirements.txt: Updates the pinned litellm-enterprise== line to 0.1.36

All three files are updated consistently and the commitizen version_files references in enterprise/pyproject.toml confirm this bump is the canonical source of truth for the enterprise package version.

Confidence Score: 5/5

Safe to merge — purely a version bump across three package/dependency files with no logic changes.

All three files are updated consistently to 0.1.36 with no logic, schema, or behavior changes. No issues found.

No files require special attention.

Important Files Changed

Filename Overview
enterprise/pyproject.toml Bumps tool.poetry version and tool.commitizen version from 0.1.35 to 0.1.36
pyproject.toml Bumps optional litellm-enterprise dependency from 0.1.35 to 0.1.36
requirements.txt Bumps pinned litellm-enterprise==0.1.35 to litellm-enterprise==0.1.36

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[enterprise/pyproject.toml\nversion = 0.1.36] -->|commitizen version_files| B[pyproject.toml\nlitellm-enterprise = 0.1.36]
    A -->|commitizen version_files| C[requirements.txt\nlitellm-enterprise==0.1.36]
    B --> D[PyPI: litellm-enterprise 0.1.36]
    C --> D
Loading

Reviews (1): Last reviewed commit: "bump litellm-enterprise==0.1.36 in requi..." | Re-trigger Greptile

@codspeed-hq

codspeed-hq Bot commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 16 untouched benchmarks


Comparing enterprise-v36 (c4805fe) with main (d2102e9)

Open in CodSpeed

@ishaan-berri
ishaan-berri merged commit 1e66050 into main Apr 5, 2026
16 of 61 checks passed
@ishaan-berri
ishaan-berri deleted the enterprise-v36 branch April 5, 2026 00:14
harish876 pushed a commit to harish876/litellm that referenced this pull request Apr 8, 2026
* bump litellm-enterprise version to 0.1.36

* bump litellm-enterprise==0.1.36 in pyproject.toml

* bump litellm-enterprise==0.1.36 in requirements.txt
fzowl pushed a commit to fzowl/litellm that referenced this pull request Jun 24, 2026
* bump litellm-enterprise version to 0.1.36

* bump litellm-enterprise==0.1.36 in pyproject.toml

* bump litellm-enterprise==0.1.36 in requirements.txt
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