fix(model_prices): add provider-announced deprecation dates for Bedrock, Mistral, Cohere and Gemini models - #36538
Conversation
…ck, Mistral, Cohere, Gemini models Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
|
Greptile SummaryAdds provider lifecycle metadata for retiring Bedrock, Cohere, Mistral, and Gemini models while keeping both model-registry copies synchronized.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| model_prices_and_context_window.json | Updates lifecycle metadata in the canonical model registry without changing pricing, limits, or routing behavior. |
| litellm/model_prices_and_context_window_backup.json | Mirrors the canonical lifecycle metadata changes in the packaged fallback registry. |
Reviews (2): Last reviewed commit: "fix(model_prices): drop unannounced shut..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
bugbot run |
| }, | ||
| "gemini/gemini-embedding-001": { | ||
| "deprecation_date": "2028-05-14", | ||
| "deprecation_date": "2026-07-14", |
There was a problem hiding this comment.
Wrong Gemini embedding deprecation date
High Severity
gemini/gemini-embedding-001 had its deprecation_date changed from 2028-05-14 to 2026-07-14, but the official Gemini API deprecations page does not list this model, and Gemini embeddings docs still describe it as available. Google Cloud documents retirement no sooner than May 20, 2028. The July 14 date appears only on third-party trackers, so deprecation alerts would treat a still-supported model as already retired.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 20c0e0d. Configure here.
| "mode": "image_generation" | ||
| }, | ||
| "twelvelabs.marengo-embed-2-7-v1:0": { | ||
| "deprecation_date": "2026-11-30", |
There was a problem hiding this comment.
Invented Marengo Bedrock EOL date
Medium Severity
twelvelabs.marengo-embed-2-7-v1:0 and its us. / eu. variants were given deprecation_date 2026-11-30, but the AWS Bedrock Marengo Embed v2.7 model card lists the model as Active with EOL N/A, and it does not appear in the Bedrock model lifecycle EOL tables. Deprecation alerts would warn about a retirement AWS has not announced.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 20c0e0d. Configure here.
There was a problem hiding this comment.
The AWS Bedrock model lifecycle page does list Marengo Embed v2.7: Legacy May 29, 2026, EOL November 30, 2026, matching this date
…models Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
2 issues from previous reviews remain unresolved.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 6ad343c. Configure here.
AWS no longer serves `anthropic.claude-3-sonnet-20240229-v1:0`. The streaming path returns a plain 404, "Model with the provided id anthropic.claude-3-sonnet-20240229-v1:0 is not found", and the non-streaming path answers 500 for the same reason. Our own cost map has carried a 2026-07-30 deprecation date for it since BerriAI#36538 That accounts for 20 failures across local_testing_part1, local_testing_part2 and llm_translation_testing. litellm maps both statuses correctly, so the tests are what went stale, not the client Replacement is `us.anthropic.claude-sonnet-4-5-20250929-v1:0`: a like-for-like Sonnet, and the newest Bedrock Sonnet this repo exercises against the real API in tests/e2e. Newer ids exist in the cost map, but nothing in the repo calls them live, so picking one would be an unverified guess about model access on the CI account Scope is limited to the tests that actually issue a request. The occurrences that assert on the model string itself, or that feed mocked transformations, keep the old id so their assertions stay meaningful


TLDR
Problem this solves:
/model/deprecationsendpoint #26900)How it solves it:
deprecation_dateto 64 Bedrock/Mistral/Cohere/Gemini entriesUser Flow
Before: an operator wants to know which of their deployed models are being retired, but most already-retired models look healthy.
mistral/mistral-large-2411,anthropic.claude-3-haiku-20240307-v1:0,cohere.command-r-v1:0After: the same lookup surfaces the provider-announced retirement dates.
"deprecation_date"(2026-05-31,2026-09-10,2026-08-19respectively)Relevant issues
Supports #26900 (proactive model deprecation alerts /
/model/deprecations). No new keys or formats were invented: the existingdeprecation_date(YYYY-MM-DD) key is used.Linear ticket
Sources for every changed value
Amazon Bedrock — EOL dates from https://docs.aws.amazon.com/bedrock/latest/userguide/model-lifecycle.html (AWS states Bedrock dates are authoritative for Bedrock, and may differ from the model provider's own schedule):
ai21.jamba-1-5-large-v1:0,ai21.jamba-1-5-mini-v1:0→ 2026-11-26amazon.nova-canvas-v1:0(+us.profile,1024-x-1024/50-steps/bedrock/…variant) → 2026-09-30us.amazon.nova-premier-v1:0→ 2026-09-14anthropic.claude-opus-4-1-20250805-v1:0(+us.) → 2027-01-08anthropic.claude-sonnet-4-20250514-v1:0(+us./eu./apac./global.) → 2026-10-14anthropic.claude-3-haiku-20240307-v1:0(+us./eu./apac.and bothbedrock/us-gov-*entries) → 2026-09-10anthropic.claude-3-sonnet-20240229-v1:0(+us./eu./apac.) → 2026-07-30apac.anthropic.claude-3-5-sonnet-20240620-v1:0,bedrock/us-gov-east-1/…,bedrock/us-gov-west-1/…→ 2026-07-30apac.anthropic.claude-3-5-sonnet-20241022-v2:0→ 2026-07-30bedrock/us-gov-west-1/anthropic.claude-3-7-sonnet-20250219-v1:0→ 2026-07-30cohere.command-r-v1:0,cohere.command-r-plus-v1:0→ 2026-08-19twelvelabs.marengo-embed-2-7-v1:0(+us./eu.) → 2026-11-30Region-scoped rows were respected: e.g. Claude 3.7 Sonnet and Claude 3.5 Sonnet v1/v2 are Legacy only in the specific regions AWS lists, so only the matching
bedrock/us-gov-*/apac.keys were dated, not the commercial base entries. Likewiseeu.anthropic.claude-opus-4-1-…was left undated (Opus 4.1 is Legacy in US regions only).Cohere — https://docs.cohere.com/docs/deprecations ("Effective April 4th, 2026, the following models will be retired"):
embed-english-v2.0,embed-english-light-v2.0,embed-multilingual-v2.0→ 2026-04-04Mistral — retirement column of the "Deprecated & retired models" table at https://docs.mistral.ai/getting-started/models/models_overview:
mistral/mistral-large-2407,mistral/open-mistral-7b,mistral/open-mixtral-8x22b,mistral/open-mixtral-8x7bmistral/open-codestral-mambamistral/codestral-2405,mistral/mistral-large-2402,mistral/mistral-medium-2312mistral/devstral-small-2505,mistral/magistral-medium-2506,mistral/magistral-small-2506mistral/pixtral-12b-2409mistral/labs-devstral-small-2512mistral/devstral-medium-2507,mistral/devstral-small-2507,mistral/mistral-large-2411,mistral/pixtral-large-2411,mistral/mistral-ocr-2505-completionmistral/devstral-2512,mistral/magistral-medium-2509,mistral/magistral-medium-1-2-2509,mistral/magistral-small-1-2-2509,mistral/mistral-small-3-2-2506,mistral/open-mistral-nemo-2407mistral/mistral-medium-2505,mistral/mistral-medium-2508,mistral/mistral-medium-3-1-2508Only dated snapshots were touched;
-latestaliases were left alone.Gemini API — shutdown dates from https://ai.google.dev/gemini-api/docs/deprecations:
gemini/gemini-2.5-flash-preview-09-2025→ 2026-02-17 (page listsgemini-2.5-flash-preview-09-25, shutdown February 17, 2026)The Gemini 2.5 GA models (
gemini-2.5-pro/-flash/-flash-lite) andgemini-embedding-001were reviewed and left untouched: the deprecations page shows "No shutdown date announced" for the three GA models, andgemini-embedding-001's existing2028-05-14already matches its published shutdown date.Pre-Submission checklist
This is a data-only change; it is covered by the existing registry schema tests rather than new tests.
Screenshots / Proof of Fix
Data-only change to the model cost map (root file plus the in-package backup copy, kept byte-for-byte in sync).
Validation at commit
6ad343c99c:Both JSON files re-parse cleanly with the same 3003 entries as before, and diff identically to each other.
Type
🐛 Bug Fix
Caveats (if any)
Link to Devin session: https://app.devin.ai/sessions/cba0163ddd974ecf909edc5178feb056
Note
Low Risk
Data-only metadata additions to the model cost map; no pricing, limits, or runtime logic changes.
Overview
Adds
deprecation_datefields to ~67 model entries across Bedrock, Mistral, Cohere, and Gemini so/model/infocan surface provider-announced retirement dates.Dates come from official lifecycle pages (AWS Bedrock, Cohere, Mistral, Gemini). Both
model_prices_and_context_window.jsonand the in-package backup stay in sync. No pricing or capability fields were changed.Reviewed by Cursor Bugbot for commit 6ad343c. Bugbot is set up for automated code reviews on this repo. Configure here.