Tin Chi Lo 8a30af69d0 fix(ui): verify and create must use the same token, not just the freshest each ... The ref fix made router creation use whichever token is current when the create call fires, but the preceding availability check still went through the query's own refetch, which stays bound to whatever token was current when that render's useQuery was set up. If the token rotated in between, that split verification from a stale caller's model list against creation under a different one, meaning the caller actually creating the router never had its own access checked. Fetch directly against accessTokenRef in the verification step too, so both calls agree on the same live identity instead of each independently chasing "freshest."		2026-08-03 18:48:23 -07:00
..
litellm-dashboard	fix(ui): verify and create must use the same token, not just the freshest each	2026-08-03 18:48:23 -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	fix(ui): serve /ui/assets from the nginx image instead of SPA fallback (#34066)	2026-07-21 09:22:02 -07:00