Yassin Kortam 104fe73113 fix(dashboard): don't show a stale provider prompt-cache chip on a response-cache hit (#37951) ... * fix(dashboard): don't show a stale provider prompt-cache chip on a response-cache hit The playground's non-streaming chat completion and responses paths replayed a cache hit's original usage payload verbatim, so ResponseMetrics kept rendering the provider's prompt-cache-write/read chips using token counts from the original request. Detect the hit via the x-litellm-cache-key response header and render a Response Cache indicator instead. * fix(dashboard): expose x-litellm-cache-key through CORS for the playground cache-hit indicator		2026-08-25 13:07:09 -07:00
..
litellm-dashboard	fix(dashboard): don't show a stale provider prompt-cache chip on a response-cache hit (#37951)	2026-08-25 13:07:09 -07:00
Dockerfile	chore(build): move the Admin UI toolchain to Node 24 (#35801)	2026-08-04 12:36:07 -07:00
nginx.conf	fix(ui): boot the UI image as an arbitrary uid by anchoring nginx writes under /tmp (#37982)	2026-08-24 11:57:36 -07:00