chore(deps): bump berriai/litellm from v1.84.4 to v1.100.1

[dependabot]

Warning

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

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

Release notes

Sourced from berriai/litellm's releases.

v1.100.1

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.100.1

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.100.1/cosign.pub \
  ghcr.io/berriai/litellm:v1.100.1

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

• chore(release): backport #39568 and #39572 to stable/1.100.x and cut 1.100.1 by @​devin-ai-integration[bot] in BerriAI/litellm#40176
• fix(router): backport #39491 to stable/1.100.x so retry breadcrumbs stop retaining every earlier request by @​devin-ai-integration[bot] in BerriAI/litellm#40455
• revert: drop the spend attribution backports from stable/1.100.x by @​devin-ai-integration[bot] in BerriAI/litellm#40495

Full Changelog: BerriAI/litellm@v1.100.0...v1.100.1

v1.100.0-dev.1

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:

... (truncated)

Commits

• 1dba17b Merge pull request #40495 from BerriAI/litellm_revert_1_100_x_spend_backports
• dec2c2a Revert "fix(spend-tracking): keep batch spend keys joinable after v1.99 prove...
• d7198f4 Revert "fix(spend-tracking): keep internal service-account key names readable...
• e4e811c Merge pull request #40455 from BerriAI/litellm_backport_1_100_x_retry_breadcr...
• a9ea571 test(router): type the breadcrumb test helpers
• 76b5fec fix(router): keep retry breadcrumbs per request and out of the request snapshot
• ecc04bf Merge pull request #40176 from BerriAI/litellm_backport_1_100_x_spend_key_hash
• 0b176c3 chore: refresh uv.lock for 1.100.1
• 8b0ae02 bump: version 1.100.0 -> 1.100.1
• c2e18a4 fix(spend-tracking): keep internal service-account key names readable in spen...
• Additional commits viewable in compare view

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]

Superseded by #270.