LiteLLM v1.105.0-rc.1
LiteLLM v1.105.0-rc.1 adds Microsoft 365 (Graph) to the MCP catalog, strengthens proxy boot and guardrail behaviors, and provides official Cosign verification instructions for Docker images.
Why this signal matters
LiteLLM has released pre-release v1.105.0-rc.1. Key updates include the addition of the Microsoft 365 (Graph) server to the Model Context Protocol (MCP) catalog and scoped SQL tracing queries. The proxy now strictly exits if database initialization fails at boot and rejects non-canonical daily activity dates. Guardrails updates include routing Straiker sk-agt keys to v3 with a fail-closed policy on missing verdicts, plus restored Azure guardrail user prompt dispatching. Stored spend logs also retain tool payloads and logprobs unmasked. Instructions for verifying the signed Docker images via Cosign using either the pinned commit hash or release tag are documented.
Actionable summary
LiteLLM v1.105.0-rc.1 introduces a Microsoft 365 MCP server, enforces proxy process termination upon database setup failure, improves Straiker and Azure guardrails, and clarifies Docker image signature verification via Cosign.
- Agent usefulness
- 94/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Verify pre-release Docker images using Cosign and the provided public key reference before deployment.
- Review proxy deployment configurations, ensuring database connectivity since startup now strictly terminates on DB setup failure.
- Validate Straiker guardrail integration if using 'sk-agt' keys due to the v3 fail-closed routing behavior.