Skip to content

chore(deps): update litellm requirement from >=1.80 to >=1.83.7 in /pb-proxy#145

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pb-proxy/litellm-gte-1.83.7
Open

chore(deps): update litellm requirement from >=1.80 to >=1.83.7 in /pb-proxy#145
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/pip/pb-proxy/litellm-gte-1.83.7

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 8, 2026

Updates the requirements on litellm to permit the latest version.

Commits

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 8, 2026

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot force-pushed the dependabot/pip/pb-proxy/litellm-gte-1.83.7 branch 2 times, most recently from 754d12b to f0387a6 Compare May 8, 2026 23:08
@7schmiede
Copy link
Copy Markdown
Member

@dependabot rebase

@dependabot dependabot Bot force-pushed the dependabot/pip/pb-proxy/litellm-gte-1.83.7 branch from f0387a6 to 02c10bf Compare May 8, 2026 23:11
Updates the requirements on [litellm](https://github.com/BerriAI/litellm) to permit the latest version.
- [Release notes](https://github.com/BerriAI/litellm/releases)
- [Commits](https://github.com/BerriAI/litellm/commits)

---
updated-dependencies:
- dependency-name: litellm
  dependency-version: 1.83.7
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/pip/pb-proxy/litellm-gte-1.83.7 branch from 02c10bf to 9e58589 Compare May 8, 2026 23:12
7schmiede added a commit that referenced this pull request May 8, 2026
Routine dependency-maintenance release on top of v0.9.2 — no
service-code changes, no DB migrations, no breaking changes. Refreshes
14 Python pin floors across mcp-server, ingestion, pb-proxy, and
reranker to the current 2026-05 upstream releases (#136#151, except
#145 which is held back: litellm 1.83.7 hard-pins pydantic==2.12.5
and conflicts with our >=2.13.4 floor; will land once upstream
relaxes the bound).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@7schmiede
Copy link
Copy Markdown
Member

Re-running CI to check if upstream litellm has shipped a python-dotenv pin relaxation since 2026-05-08.

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.

1 participant