Skip to content

chore(ci): bump deps#30899

Merged
yuneng-berri merged 3 commits into
litellm_internal_stagingfrom
litellm_bump_jun20
Jun 20, 2026
Merged

chore(ci): bump deps#30899
yuneng-berri merged 3 commits into
litellm_internal_stagingfrom
litellm_bump_jun20

Conversation

@yuneng-berri

Copy link
Copy Markdown
Collaborator

Relevant issues

Linear ticket

Pre-Submission checklist

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

  • I have added meaningful tests
  • 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

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

@yuneng-berri yuneng-berri requested a review from a team June 20, 2026 22:14
@greptile-apps

greptile-apps Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Routine version bump incrementing litellm from 1.89.0 to 1.90.0 and litellm-enterprise from 0.1.42 to 0.1.43, with the lock file updated accordingly.

  • pyproject.toml: version and [tool.commitizen] version updated to 1.90.0; litellm-enterprise pin updated to 0.1.43.
  • enterprise/pyproject.toml: version and [tool.commitizen] version updated to 0.1.43.
  • uv.lock: Package versions aligned and exclude-newer timestamp advanced from 2026-06-16 to 2026-06-17.

Confidence Score: 5/5

Safe to merge — changes are limited to version number increments and the generated lock file.

Only three files are touched: the two pyproject.toml manifests and the uv.lock file. All edits are version string replacements and a lock-file timestamp advance; there is no production logic, API surface, or schema change.

No files require special attention.

Important Files Changed

Filename Overview
pyproject.toml Version bump from 1.89.0 to 1.90.0 and updates litellm-enterprise pin from 0.1.42 to 0.1.43
enterprise/pyproject.toml Enterprise package version bumped from 0.1.42 to 0.1.43 in both project and commitizen sections
uv.lock Lock file updated to reflect new litellm (1.90.0) and litellm-enterprise (0.1.43) versions, and the exclude-newer timestamp advanced by ~1.7 days

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

@codecov

codecov Bot commented Jun 20, 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 merged commit 46d2861 into litellm_internal_staging Jun 20, 2026
117 of 122 checks passed
@yuneng-berri yuneng-berri deleted the litellm_bump_jun20 branch June 20, 2026 22:40
fzowl pushed a commit to fzowl/litellm that referenced this pull request Jun 24, 2026
* bump: version 0.1.42 → 0.1.43

* bump: version 1.89.0 → 1.90.0

* adding uv lock
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