Repository navigation
chore(cost-map): take azure_ai claude 4.5 retirement dates from the Azure schedule - #43846
berriai-litellm-provider-info-sync[bot] wants to merge 1 commit into
Conversation
…zure schedule Price-Sync: litellm-providers
|
|
|
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 744e4a5. Configure here.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…he Azure schedule Supersedes: #43846 Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
Superseded by the rolling registry PR #43857, which carries these three azure_ai Claude 4.5 retirement dates and the source field. Each date was re-checked against the raw rows on the Azure retirement schedule |
Summary
The Azure retirement schedule now lists later retirement dates for the three Claude 4.5 models sold through Foundry. The catalog still carried 2026-10-19 on all three rows. Per ruling
azure-conflicting-dates-latest-winsthe latest date wins fordeprecation_dateRows
azure_ai/claude-sonnet-4-5azure_ai/claude-opus-4-5azure_ai/claude-haiku-4-5Source: https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule (table "Foundry Models from partners and community", Anthropic section, columns Model, Version, Lifecycle, Retirement date, Replacement)
azure_ai/claude-sonnet-4-5: "claude-sonnet-4-5 | 1 | GA | 2026-11-15 | —"azure_ai/claude-opus-4-5: "claude-opus-4-5 | 1 | GA | 2026-11-24 | —"azure_ai/claude-haiku-4-5: "claude-haiku-4-5 | 1 | GA | 2026-11-15 | — and claude-haiku-4-5 | 2 | GA | 2026-11-15 | —"No prices change. The price API returned no candidates for this run and the changed pricing pages (aoai, cohere, fireworks, grok, microsoft, mistral-ai, model-router) state the same prices the catalog already carries
Rulings applied
azure-conflicting-dates-latest-wins: other date conflicts (azure/gpt-4o-transcribe 2026-12-31 vs schedule 2026-10-15, azure/gpt-4.1-nano, azure/gpt-realtime-2.1 and -mini) already carry the latest date and stay unchangedazure-mistral-large-conflicting-retirement-stay-undated: azure/mistral-large-2402 and azure/mistral-large-latest stay undatedazure-claude-mythos-leave-out-until-priced: no rows added for the Claude Mythos previewsazure-embed-v-4-0-keep-128000-input: azure_ai/embed-v-4-0 keeps 128000 inputDelisted by the provider
63 of the dispatcher's delisted ids are a naming mismatch, the eastus2 Models API lists them as
OpenAI.<model>.<version>. These are absent from the list and stay in the catalog for a human to decide:azure/ada,azure/chat-latest,azure/command-r-plus,azure/computer-use-preview,azure/container,azure/gpt-3.5-turbo,azure/gpt-3.5-turbo-instruct-0914,azure/gpt-35-turbo,azure/gpt-35-turbo-16k,azure/gpt-35-turbo-16k-0613,azure/gpt-35-turbo-instruct,azure/gpt-35-turbo-instruct-0914,azure/gpt-4,azure/gpt-4-0125-preview,azure/gpt-4-0613,azure/gpt-4-1106-preview,azure/gpt-4-32k,azure/gpt-4-32k-0613,azure/gpt-4-turbo,azure/gpt-4-turbo-vision-preview,azure/gpt-4.5-preview,azure/gpt-5-chat,azure/gpt-5.1-chat,azure/gpt-5.2-chat,azure/gpt-5.2-pro,azure/gpt-5.3-chat,azure/gpt-5.5-pro,azure/gpt-5.6,azure/mistral-large-2402,azure/mistral-large-latest,azure/o1-mini,azure/o3-deep-research,azure/o3-pro,azure/sora-2-pro,azure/sora-2-pro-high-res,azure/tts-1,azure/tts-1-hd,azure/whisper-1Note
Low Risk
Static catalog JSON updates with no pricing or runtime logic changes; only affects displayed retirement metadata for three models.
Overview
Updates Azure Foundry Claude 4.5 catalog metadata in
model_prices_and_context_window.jsonand its backup to match Microsoft’s current retirement schedule.deprecation_datemoves from2026-10-19to2026-11-15forazure_ai/claude-haiku-4-5andazure_ai/claude-sonnet-4-5, and to2026-11-24forazure_ai/claude-opus-4-5. Each of those three entries also gains asourceURL pointing at the Azure model retirement schedule doc.Pricing and capability fields are unchanged; this is a date-and-provenance sync only.
Reviewed by Cursor Bugbot for commit 744e4a5. Bugbot is set up for automated code reviews on this repo. Configure here.