Tools
LiteLLM proxy starts authorizing every Responses API id, not only the ones it issued
PR #39548 in the v1.102.0-rc.1 release changes the proxy to run authorization on every Responses API id rather than trusting ids the proxy itself minted, closing a path where a caller could reference someone else's response object. The same release partitions user-key objects into their own in-memory cache (#40713), keeps an open Redis circuit breaker open and quiet on the sync read and spend-counter paths (#40624), and stops logging the request payload as `guardrail_response` on pre_call hooks (#39699). PR #40190 restores credential coverage that a 4.5 entropy limit had silently dropped from secret hiding.
Source
↳ Follow the thread