litellm/ui
Vivswan Shah bca69f4439 feat(proxy): declare response models for /model/info, /v1/model/info and /model_group/info
The three routes were served without a response schema, so /openapi.json published an empty schema for their 200 bodies and a client generating types from the document got unknown for each

ModelGroupInfoResponse and ModelInfoV1Response, both named ResourceResponse envelopes, now back the route decorators. /model_group/info returns the model, so FastAPI serializes it. /model/info keeps its orjson Response, so there the model documents the body: a list of deployments, or the single deployment object the proxy serves when started from the CLI with --model, whose litellm_params carry every unset non-secret value as the string None, which is why the params are a wire-specific model rather than the router's input type

The dashboard's generated schema.d.ts is regenerated with npm run gen:api
2026-10-08 05:48:40 -04:00
..
litellm-dashboard feat(proxy): declare response models for /model/info, /v1/model/info and /model_group/info 2026-10-08 05:48:40 -04:00
Dockerfile fix(docker): bump nginx runtime to 1.31.5-alpine3.24 and pin digest to resolve critical CVEs (#39561) 2026-09-03 08:46: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