jesus-berri 3b62b6311c fix(proxy): make /update/sso_settings a true PATCH and send only changed SSO fields from the UI (#49527) ... * fix(proxy): make /update/sso_settings a true PATCH and send only changed SSO fields from the UI * fix(proxy): mask SSO client secrets in the /update/sso_settings response * fix(proxy): keep SSO values that only live in the environment_variables row on a partial SSO PATCH The SSO PATCH strips every SSO env var from the environment_variables config row. Now that the UI only sends changed fields, an omitted value that lived only in that row was dropped from both tables and lost on restart. Carry those values into the SSO row before stripping them * test(ui): pin CLEARED_SSO_SETTINGS to exactly the backend SSOConfig fields With PATCH semantics an omitted key keeps its stored value, so a field missing from the Clear list would silently survive Clear SSO settings		2026-11-02 09:14:10 -08:00
..
docker-entrypoint.d	feat(helm): support a separate hostname per component in the componentized deploy (#46360)	2026-10-14 14:56:36 -07:00
litellm-dashboard	fix(proxy): make /update/sso_settings a true PATCH and send only changed SSO fields from the UI (#49527)	2026-11-02 09:14:10 -08:00
Dockerfile	build(docker): refresh base images and ship only runtime files in component images (#48279)	2026-10-24 22:33:45 -07:00
nginx.conf	feat(helm): support a separate hostname per component in the componentized deploy (#46360)	2026-10-14 14:56:36 -07:00