# LiteLLM v1.103.0-rc.1

Category: model-behavior
Published: 2026-09-20T07:10:47Z
Source: [LiteLLM releases](https://github.com/BerriAI/litellm/releases/tag/v1.103.0-rc.1)
Agent usefulness: 82/100
Confidence: 0.96
Content mode: release-watch
Verified: 2026-09-23T06:17:48.112Z
Tags: gateway, models, observability

## Human Summary
LiteLLM v1.103.0-rc.1 introduces 429 rejections for saturated deployment slots, Microsoft Foundry agent connectivity via Entra auth, Amazon Transcribe passthrough, and various proxy performance and routing fixes.

## Agent Summary
LiteLLM release v1.103.0-rc.1 adds router-level 429 rejections when max parallel request slots fill, integration for Microsoft Foundry agents via Entra auth, live MCP gateway session tracking, off-event-loop prompt injection heuristics, and deferred imports of fastapi and tiktoken. Configuration resolution was refactored so config files supersede the database.

## Body
LiteLLM v1.103.0-rc.1 is a release candidate containing numerous proxy, routing, and provider integration updates. Key additions include 429 status rejections when deployment max parallel request slots are exhausted, integration with Microsoft Foundry agents via Entra auth, support for Amazon Transcribe pass-through with completion-time job pricing, live MCP gateway session visibility, and separate login/secret namespaces for HashiCorp Vault. The release also shifts prompt injection heuristics off the main event loop, ensures config files take precedence over database configurations, evicts JWT key mapping caches on entity deletion, optimizes startup times by deferring FastAPI and Tiktoken imports, and resolves various pricing and cost calculation edge cases across Mistral, Bedrock Titan, and OpenRouter.

## Recommended actions
- Verify the container image using Cosign against key commit 0112e53 or tag v1.103.0-rc.1 if deploying via Docker.
- Review deployment routing configurations to account for immediate 429 rejections when max parallel request slots are saturated.
- Ensure deployment settings reflect the new precedence rule where config file definitions override database values.

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