There is a date. Build the replacement against your dataset while the current model still answers, compare the two, and move before the deadline rather than on it.
A retirement or a withdrawal. The deadline is the provider's, and it does not move for you.
Google limited access to Gemini 2.5 models to projects that are actively using them. The entry points developers to Gemini 3.5 Flash-Lite or Gemini 3.8 Flash instead.
Chat assistant: A forced move changes the model behind every answer. Google's own documentation says most production apps should use a specific stable model, and hedges only that stable models usually do not change.
RAG: When the generating model is replaced, the answer is scored again for faithfulness, which Ragas defines as the share of claims in a response that can be inferred from the retrieved context. It scores grounding in that context, not factual truth.
Plan a migrationCheck whether any project still calls a Gemini 2.5 model id, and open a migration ticket for the ones that do before new projects lose access.
OpenAI announced on August 26, 2026 that whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe and gpt-4o-transcribe-diarize are scheduled to shut down on February 26, 2027. The recommended replacements are gpt-live-transcribe and gpt-transcribe.
Summarisation: Arize Phoenix writes that end to end evaluation only inspects the two endpoints, the input and the final output, and that the interesting failures happen in the middle. A transcript sits in that middle, so a summary scored only on its final text does not show which step changed.
Plan a migrationFind every call to one of the four ids, run a held out set of recordings through gpt-transcribe or gpt-live-transcribe, and keep both transcripts so the step after them can be compared before February 26, 2027.
Anthropic released v1.0 of the Python SDK. It requires Python 3.10 or later and removes long deprecated surface, including the legacy Text Completions API and the temperature, top_p and top_k parameters on Messages methods. Anthropic's deprecations page states that passing them on v1.0 and later raises a TypeError.
Generation: This is caller code breaking with no model swap on your side. Anthropic deprecated temperature, top_p and top_k from Claude Opus 4.7 onward, and a non-default value returns a 400 error. It is a parameter deprecation; nothing is published about an effect on output quality.
Plan a migrationSearch your code for temperature, top_p and top_k on Messages calls and remove them, and pin your Python SDK version until that change is made.
Anthropic removed fast mode for Claude Opus 4.6. Requests to claude-opus-4-6 with speed set to fast no longer run at fast speed or premium pricing: they run at standard speed, are billed at standard rates, and do not return an error. The usage.speed field on the response reports the speed used, and Anthropic says to migrate to Claude Opus 4.8 to continue using fast mode.
Plan a migrationA request that asks for fast mode on this id still succeeds, so read usage.speed in your own logs to see which speed you are getting, and move to Claude Opus 4.8 if the feature depends on it.
Anthropic announced the deprecation of Claude Opus 4.1, claude-opus-4-1-20250805, with retirement on the Claude API scheduled for August 5, 2026. Anthropic recommended migrating to Claude Opus 4.8.
Chat assistant: Anthropic notified developers on 5 June 2026 that Claude Opus 4.1 would be retired on 5 August 2026, with Claude Opus 4.8 as the recommended replacement. Nothing is published about how the replacement behaves differently, so a forced swap changes the model behind every answer with no provider figure to compare against.
Plan a migrationThe retirement date has passed, so any call still naming claude-opus-4-1-20250805 fails. Confirm nothing does, and record which id your feature runs on now.
OpenAI announced the deprecation of reusable prompt objects, the Evals platform and Agent Builder. The v1/prompts API and reusable prompt objects, the Evals dashboard and API, and Agent Builder are scheduled to shut down on November 30, 2026, and existing evals become read only on October 31, 2026. OpenAI says to move reusable prompt content into your application code, and points to the Agents SDK, ChatGPT Workspace Agents and Promptfoo.
Plan a migrationList every place that loads a prompt by id from v1/prompts or runs a job on the Evals platform, and put the move into application code or another runner on the calendar before October 31, 2026.
Anthropic retired the 1M token context window beta, context-1m-2025-08-07, for Claude Sonnet 4.5 and Claude Sonnet 4. The beta header now has no effect on these models, and requests exceeding the standard 200k token context window return an error. Anthropic says to migrate to Claude Sonnet 4.6 or Claude Opus 4.6, where the 1M context window is included at standard pricing with no beta header required.
RAG: A smaller usable window changes how much retrieved text reaches the model. Ragas defines faithfulness as the share of claims in a response that can be inferred from the retrieved context, so the scorer reads what was actually passed in, not what was retrieved.
Plan a migrationFind any request that still sends the context-1m-2025-08-07 header to these two ids, then either shorten the input or move the feature to a model where the 1M window is standard.
On April 14, 2026, Anthropic notified developers using Claude Sonnet 4 and Claude Opus 4 of their upcoming retirement on the Claude API. Both models retired on June 15, 2026, with claude-sonnet-4-6 and claude-opus-4-8 listed as the recommended replacements.
Chat assistant: The clock on a retirement belongs to the provider. Anthropic says it gives customers with active deployments at least 60 days' notice before retiring a publicly released model, and its page states that partner platforms such as Amazon Bedrock and Google Cloud set their own schedules.
Summarisation: A recommended replacement writes summaries in its own register. Galtea warns against updating ground truth to match model behaviour, so the expected outputs stay where they are and the gap is what gets reported.
Plan a migrationExport your Claude API usage by model and confirm nothing still calls these two dated ids, since requests to them now return an error.
RAG: A retrieval feature pinned to a preview id can lose that id on short notice. Google says Gemini preview models may be used in production but will be deprecated with at least 2 weeks' notice.
Classification: A classifier that runs unattended is the last place a shutdown gets noticed. Google's documentation says most production apps should use a specific stable model, and hedges that stable models usually do not change.
Plan a migrationReplace any gemini-3-pro-preview pin with a current Gemini 3 id and rerun the affected suites, since the preview id no longer serves.
Anthropic launched automatic caching for the Messages API, where a single cache_control field caches the last cacheable block and the cache point moves forward as a conversation grows. The same entry retired Claude Sonnet 3.7, claude-3-7-sonnet-20250219, and retired Claude Haiku 3.5, claude-3-5-haiku-20241022, on the Claude API. Anthropic recommends upgrading to Claude Sonnet 4.6 and Claude Haiku 4.5.
RAG: When the generating model is replaced, the answer is scored again for faithfulness, which Ragas defines as the share of claims in a response that can be inferred from the retrieved context. It scores grounding in that context, not factual truth.
Plan a migrationCheck that nothing still names either retired id, since Anthropic says requests to retired models fail, and decide separately whether automatic caching should be switched on for your long conversations.
OpenAI announced the deprecation of the chatgpt-4o-latest snapshot on November 18, 2025, with a shutdown date of February 17, 2026. The recommended replacement is gpt-5.1-chat-latest.
Chat assistant: How much warning a snapshot gets depends on its class. OpenAI says it gives at least 6 months' notice before retiring a generally available model, at least 3 months for specialized variants, and that preview models may be retired with much shorter notice, such as 2 weeks, with no minimum committed.
Generation: Prompts tuned against the old snapshot produce different text on the replacement. Galtea warns against updating ground truth to match model behaviour.
Plan a migrationSearch your configuration for chatgpt-4o-latest and move those calls to gpt-5.1-chat-latest, then rerun the prompts that were tuned for the old snapshot.
On October 28, 2025, Anthropic notified developers using Claude Sonnet 3.7 of its upcoming retirement on the Claude API. The model retired on February 19, 2026, with claude-sonnet-4-6 listed as the recommended replacement.
Classification: A retired id stops serving, so an unattended classifier fails outright rather than quietly scoring worse. Anthropic says it gives customers with active deployments at least 60 days' notice before retiring a publicly released model, and states that partner platforms set their own schedules.
Generation: Prompts written for the retired model produce different text on the replacement. Galtea warns against updating ground truth to match model behaviour.
Plan a migrationConfirm that nothing still calls claude-3-7-sonnet-20250219, since requests to the retired id now fail, and rerun the prompts that were written for it.
OpenAI announced on September 26, 2025 the deprecation of gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106, with a shutdown date of September 28, 2026. The listed migration target is gpt-5.6-terra.
Classification: Older ids tend to sit in batch jobs and internal classifiers that nobody watches. OpenAI says it gives at least 6 months' notice before retiring a generally available model, at least 3 months for specialized variants, and that preview models may be retired with much shorter notice, such as 2 weeks, with no minimum committed.
Extraction: Moving an extractor onto a current model is a release like any other. Galtea recommends a tiered release gate in which blocking failures such as safety or policy violations block a deploy at any rate, while regressions gate on the change in fail rate.
Plan a migrationCheck batch jobs and older internal tools for these four ids ahead of the stated shutdown date, and move any remaining traffic to a current model.
Change-log entries restate provider announcements with sources and dates. Impact notes cite public practitioner reports. The site publishes no measurements of its own on any model.
Questions about this action
Who decides the recommended action?
We do, from what the provider announced, and it is one of exactly four: rerun, re-pin, re-prompt or migrate. It is a statement about what a team does this week, not a prediction about your feature.
Does an action mean something is wrong with my feature?
No. It means something your feature depends on moved. Whether anything about your output changed is a question only a rerun against your own dataset can answer.
What happens if we are on a plan?
A tracked provider update triggers a rerun of your suite within 2 business days of the provider's announcement, and you get a written verdict. That is one of the six written guarantees on every plan.