Best OpenAI migration feed: OpenAI API changelog. Official OpenAI release log for launches, pricing, and renamed features. Use it to catch live changes like pricing moves, feature renames, and model guidance shifts before rewriting a workflow.
Best Anthropic retirement source: Claude model deprecations. Official Anthropic retirement schedule and replacements. Use it before pinning Claude model IDs or teaching teams to rely on an older snapshot.
Best Gemini shutdown source: Gemini deprecations. Official Gemini API deprecation schedule. Use it when Google preview and Flash variants are moving quickly and you need the replacement path from the primary source.
Best Anthropic upgrade checklist: Anthropic migration guide. Official Claude migration guide covering current model deltas and breaking changes. Use it when you are changing Claude model IDs and need to re-check effort, tool behavior, prompt caching, or system-message differences.
Best Perplexity platform migration source: Perplexity migrate from Sonar to Agent API. Official Perplexity migration guide from Sonar to the Agent API. Use it when old Perplexity integrations still assume chat completions instead of the newer agent-first API.
Best DeepSeek migration source: DeepSeek V4 Preview release. Official DeepSeek V4 release note and alias migration notice. Use it when a provider is moving old aliases to new V4 families and you want the exact date and replacement models.
Release notes are part of the learning stack now
If you build with frontier models, release notes and deprecation pages are no longer optional reading. Model aliases change, pricing changes, feature flags move, APIs get renamed, and a previously good course can become subtly wrong if it assumes an older default.
As of Monday, August 17, 2026, the pattern is clear across providers: OpenAI's changelog still carries the concrete pricing and feature updates around GPT-5.6 and Fast mode, its Assistants migration guide still points to the August 26, 2026 shutdown date, OpenAI Academy is actively publishing Codex and builder bootcamp material for API foundations, agents, MCP, and advanced automation, Gemini's changelog and deprecations pages now document the August 13, 2026 Gemini 3.7 Flash GA release alongside the newer webhook-backed async workflow surface and the August 17, 2026 Imagen shutdown notice, Anthropic's release notes now include the August 7, 2026 Managed Agents session-budget update alongside its broader Claude 5-era migration and deprecation guidance, Meta's Model API docs now matter alongside classic Llama docs for hosted coding and agent workflows, xAI's model and Build docs now center Grok 4.6 and Build behavior, Perplexity's split between Search API and Agent API is clearer in the current docs, OpenRouter's response-caching and ZDR docs now matter for operational routing decisions, and DeepSeek's August 13, 2026 V4-Pro GA release note plus pricing and Codex integration pages explain the current V4 family and the retirement of older aliases after July 24, 2026.
What to bookmark by default
Keep one model catalog page and one release or deprecation page open for each provider you actually use. For OpenAI that usually means the model guide plus the changelog or deprecations page. For Anthropic it means the Claude models overview plus release notes or model deprecations. For Gemini it means the models page plus the changelog and deprecations page. For DeepSeek it means pricing or updates plus the live model list.
When you use a routing layer such as OpenRouter, keep both the provider docs and the routed catalog open. The routed view helps you see availability, aliases, and market movement. The provider view tells you what the model is supposed to do and what changed.
How to keep apps and coding agents current
Do not rely on `latest` or family aliases blindly unless you also have evals and regression checks. A safer workflow is to watch release notes, shortlist the affected models, run a small eval set, compare latency and cost, and then update the default for your app, coding agent, or internal tool.
This matters even more for coding agents and deep-research tools because they depend on tool use, output structure, and long-running behavior. A migration that looks small on a model card can still change how an agent plans, reasons, or uses budget.
Recommended courses and resources
-
The AI Engineer Roadmap
Free tutorial · Matt Pocock · Beginner to intermediate
You want a guided path through core AI concepts, model selection, the AI engineering mindset, evals, and techniques for improving LLM-powered apps.
-
OpenAI external models
Guide · OpenAI · Intermediate
You want to learn how OpenAI handles access to non-OpenAI model families before designing a mixed-provider or routed workflow.
-
OpenAI model guide
Model docs · OpenAI · Beginner to advanced
You need to choose between current GPT-5.6 variants, smaller GPT-5.4 variants, reasoning levels, tool support, and cost-sensitive API paths, including the current default starting points of GPT-5.6 Sol, Terra, and Luna.
-
OpenAI model selection
Guide · OpenAI · Intermediate
You want OpenAI's official framework for balancing accuracy, latency, and cost instead of choosing a model family by brand familiarity alone.
-
OpenAI API changelog
Release notes · OpenAI · Intermediate
You want the official running log of OpenAI API launches, pricing shifts, renamed features, and model changes before updating a workflow or teaching page.
Common questions
Which AI release notes should I actually follow?
Follow the official changelog or release-note page for every provider you actively use, plus its deprecations or shutdown page if available. OpenAI, Anthropic, Gemini, DeepSeek, Mistral, xAI, and OpenRouter all publish enough primary-source change data now that third-party summaries should be secondary.
Where can I track model deprecations and migrations across providers?
Use OpenAI deprecations, Claude model deprecations, Gemini deprecations, DeepSeek updates and pricing, Mistral changelog, and xAI release notes. Pair those with the provider's model catalog so you can see both replacements and current IDs.
How do I keep coding agents and AI apps current when model aliases change?
Watch the release notes, keep evals for your core workflows, compare the replacement model on your own prompts, and only then update the default model or alias. Treat migrations as engineering changes, not just documentation housekeeping.
