# LiteLLM v1.101.0

Category: model-behavior
Published: 2026-09-15T03:41:59Z
Source: [LiteLLM releases](https://github.com/BerriAI/litellm/releases/tag/v1.101.0)
Agent usefulness: 82/100
Confidence: 0.96
Content mode: release-watch
Verified: 2026-09-19T00:17:46.117Z
Tags: gateway, models, observability

## Human Summary
LiteLLM releases published LiteLLM v1.101.0. Verify Docker Image Signature All LiteLLM Docker images are signed with cosign (https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in commit 0112e53 (https://github.com/BerriAI/litellm/commit/0112e53046018d726492c814b3644b7d376029d0). Verify using the pinned commit…

## Agent Summary
Treat LiteLLM v1.101.0 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.

## Body
LiteLLM releases published LiteLLM v1.101.0. This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: Verify Docker Image Signature All LiteLLM Docker images are signed with cosign (https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in commit 0112e53 (https://github.com/BerriAI/litellm/commit/0112e53046018d726492c814b3644b7d376029d0). 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: bash 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: bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.101.0/cosign.pub \…

## Recommended actions
- Review the official LiteLLM releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.