litellm - 💡(How to fix) Fix [Bug]: Admin UI "Add Model" dropdown lists models past their deprecation_date

Check for existing issues

• I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

In the Admin UI "Add Model" flow, selecting a provider lists models that are already retired. getProviderModels() (ui/litellm-dashboard/src/components/provider_info_helpers.tsx) returns every cost-map entry whose litellm_provider matches the selected provider and does not filter on deprecation_date.

deprecation_date is an existing field in the cost map; 58 entries already carry it (e.g. azure/gpt-3.5-turbo-0125, deprecation_date 2025-03-31, still present). Because the dropdown ignores it, models past their deprecation date keep being offered. SambaNova is the most visible case: 12 of its 17 listed entries are retired.

Expected: the dropdown excludes entries whose deprecation_date is in the past (or shows them disabled). This applies to every provider, not just SambaNova.

Steps to Reproduce

1. Open the Admin UI (/ui) → Models → Add Model
2. Select a provider that has deprecation_date-tagged models:
   - SambaNova, or Azure OpenAI, etc.
3. Observe that the model dropdown lists retired models, e.g.:
   - SambaNova: Meta-Llama-3.1-405B-Instruct, QwQ-32B, Qwen2-Audio-7B-Instruct, ...
   - Azure: past-deprecation_date gpt-3.5-turbo variants

The dropdown is built by getProviderModels(provider, modelMap), which iterates Object.entries(modelMap) and pushes every key whose litellm_provider matches; there is no deprecation_date check.

Relevant log output

# n/a (UI behavior)

What part of LiteLLM is this about?

UI Dashboard

What LiteLLM version are you on?

v1.83.14-stable (also reproduces on main)

Proposed fix

• In getProviderModels(), skip entries whose deprecation_date is earlier than the current date (or render them disabled). Benefits all providers.

Note: tagging SambaNova's retired models with deprecation_date is handled in a separate cost-map data issue (#29011); this issue is about the UI honoring that field.