LiteLLM v1.106.3
LiteLLM v1.106.3 rotates the cosign image-signing key for Docker images and Helm charts, and removes the eMudhra root CA from trusted certificate bundles.
Why this signal matters
LiteLLM release v1.106.3 includes an important update to its image-signing infrastructure. Beginning with this release (and backported to versions 1.103.8, 1.104.6, and 1.105.4), Docker images and Helm charts are signed using a new cosign key from commit e82a3c6. Verifications using the prior key from commit 0112e53 will fail, requiring updates to verification scripts, CI pipelines, and Kubernetes admission controllers such as Kyverno, Sigstore policy-controller, or Connaisseur. Additionally, the eMudhra root CA has been removed from all certificate bundles trusted by the SDK, proxy, and Docker images.
Actionable summary
LiteLLM v1.106.3 introduces a breaking deployment change by updating the cosign public key (SHA-256: e3fe3e08c44b16407fe0b37c43b4f8b603b3a0f4ee74c29e647bc022d762c2c0) used for image/chart verification, causing older verification keys to fail. It also removes the eMudhra root CA across SDK, proxy, and Docker certificate bundles.
- Agent usefulness
- 74/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Update cosign verification scripts, CI checks, and admission policies (e.g., Kyverno, Sigstore policy-controller, Connaisseur) with the new cosign.pub from commit e82a3c6 (SHA-256:…
- Verify that services relying on the LiteLLM SDK, proxy, or container images do not depend on the removed eMudhra root CA for TLS connections.