LiteLLM v1.103.1 (PyPI ~2026-09-29T23:36Z; 5 commits ahead of 1.103.0) backports binding UI/CLI session tokens to their own AES-GCM encryption context (a80eaca), with e2e/OIDC and auth unit tests—security hardening for operators pinned on the 1.103.x stable line.
Key Takeaways
- ✓Release v1.103.1; 5 commits vs v1.103.0
- ✓Security: bind UI/CLI session tokens to dedicated AES-GCM context (
a80eaca) - ✓Tests: session-token e2e + OIDC Playwright login specs
- ✓Stable-line patch after 1.103.0; do not confuse with 1.104/1.105 pre-releases
- ✓
pip install 'litellm==1.103.1'; https://docs.litellm.ai/docs/ ; https://pypi.org/project/litellm/1.103.1/
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background
Proxy UI/CLI session tokens need isolated AES-GCM contexts. Operators pinned on 1.103.x need a stable-line security backport rather than jumping to RC/dev.
What shipped
v1.103.1: bind UI/CLI session tokens to their own AES-GCM context (a80eaca) with e2e/OIDC tests. 5 commits ahead of 1.103.0.
Benchmarks
No latency benchmarks—auth hardening only. Anchors: ahead_by 5; PyPI 1.103.1.
Get started
pip install 'litellm==1.103.1'. Docs: https://docs.litellm.ai/docs/
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.