Skip to content

chore(deps): bump berriai/litellm from v1.84.4 to v1.101.0 - #270

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker_compose/berriai/litellm-v1.101.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker_compose/berriai/litellm-v1.101.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Cooldown could not be applied because no publication date was available from the registry.

Bumps berriai/litellm from v1.84.4 to v1.101.0.

Release notes

Sourced from berriai/litellm's releases.

v1.101.0

Verify Docker Image Signature

All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53.

Verify using the pinned commit hash (recommended):

A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \
  ghcr.io/berriai/litellm:v1.101.0

Verify using the release tag (convenience):

Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules:

cosign verify \
  --key https://raw.githubusercontent.com/BerriAI/litellm/v1.101.0/cosign.pub \
  ghcr.io/berriai/litellm:v1.101.0

Expected output:

The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key

What's Changed

... (truncated)

Commits
  • 18243cd Merge pull request #40886 from BerriAI/litellm_backport_redis_chaos_rc_1_101_0
  • abfb2cf test(load): backport Redis chaos qualification to rc/1.101.0 (#40482)
  • c1a834b fix(caching): backport Redis breaker recovery guards to rc/1.101.0 (#40624)
  • ca4a613 fix(redis): backport quiet breaker refusals to rc/1.101.0 (#40620)
  • c324a2b perf(proxy): backport pipelined spend counters to rc/1.101.0 (#40371)
  • 912a3f8 Merge pull request #40346 from BerriAI/litellm_backport_40335_rc_1_101_0
  • bcddffc fix(otel): backport auth spans and callback merge to rc/1.101.0
  • f0b6d66 Merge pull request #40325 from BerriAI/litellm_backport_37667_rc_1_101_0
  • f41fc71 Merge pull request #40324 from BerriAI/litellm_backport_40312_rc_1_101_0
  • b6e73cc feat(team): backport team admin callbacks to rc/1.101.0
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker_compose Pull requests that update docker_compose code labels Sep 15, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner September 15, 2026 08:10
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker_compose Pull requests that update docker_compose code labels Sep 15, 2026
@subpath

subpath commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

@noahpodgurski @FieldMarshallObvious @ti3x This is actually pretty cool!
The CI caught a regression 🎉

In v1.84.4: TPM enforcement only tracks actual accumulated usage after each call. A call is admitted as long as current usage hasn't crossed the limit yet. So basically if we have TPM 100 and a call have 200 tokens in the current version it will be allowed but next call will be blocked for the remaining of the minute.

In the new v1.101.0: they've added a pre-flight check that compares the requested max_tokens against remaining quota, before any usage happens. If max_tokens alone exceeds the limit, it's rejected immediately: the 200 Tokens call will be rejected with TPM 100

WDYT? We could modify the test and accept that new behavior

Bumps the pinned LiteLLM image tag. This upgrade currently fails
src/tests/litellm_compatibility: v1.101.0 rejects a completion request
whenever max_tokens exceeds the end-user's tpm_limit, regardless of
remaining budget -- MLPA defaults max_tokens to 8192 (MAX_COMPLETION_TOKENS)
while most tpm_limits are 2000. Not yet resolved.
@subpath
subpath force-pushed the dependabot/docker_compose/berriai/litellm-v1.101.0 branch from 469cfdf to 3abe676 Compare September 17, 2026 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file docker_compose Pull requests that update docker_compose code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant