Tin Chi Lo c8ef01bfbe feat(mcp): make allowed_response_headers configurable from the database and dashboard ... The field was config.yaml only, so a server created through the dashboard or the REST API could never surface upstream response headers. Adds the column to all three prisma schemas plus a migration, carries it through the create, edit and temporary-record paths, the row -> MCPServer build, and the dashboard's edit form and detail view. The unsupported-transport warning now also fires for servers loaded from the database, since the dashboard can create the same misconfiguration as config.yaml. The column is a Prisma String[], which rejects null, and the edit form clears a field to null, so an explicit null normalizes to [] alongside allowed_tools.		2026-07-16 16:43:53 -07:00
..
litellm-dashboard	feat(mcp): make allowed_response_headers configurable from the database and dashboard	2026-07-16 16:43:53 -07:00
Dockerfile	feat: add componentized proxy deployment with gateway, backend, ui, and migrations (#27557)	2026-05-16 09:25:17 -07:00
nginx.conf	feat: add componentized proxy deployment with gateway, backend, ui, and migrations (#27557)	2026-05-16 09:25:17 -07:00