DeepSeek's current docs still warn that `deepseek-chat` and `deepseek-reasoner` will be retired on July 24, 2026, making V4 model-name cleanup a near-term production task
Checked on July 5, 2026: DeepSeek's official homepage still anchors the official `@deepseek_ai` X presence, but the strongest current first-party developer signal is in the API docs and changelog, which both keep the July 24, 2026 retirement warning for `deepseek-chat` and `deepseek-reasoner` while pointing users to explicit `deepseek-v4-flash` and `deepseek-v4-pro` model names.
Accepted official-source monitoring note
Today's publish-safe item stays DeepSeek-first and uses backup official documentation because the live @deepseek_ai timeline still was not safely readable in this run. DeepSeek's English homepage still anchors the official X account through the V4 Preview banner, but that banner is older and not the strongest current support signal for developers maintaining production API routes.
The stronger current first-party signal is that DeepSeek's official API docs still place the same concrete retirement warning in two prominent places: the API quick-start and the change log both say deepseek-chat and deepseek-reasoner will be discontinued on July 24, 2026 at 15:59 UTC.
What we verified on July 5, 2026
- DeepSeek's official homepage still anchors the official X account through the V4 Preview banner, confirming
@deepseek_airemains the first-source account surface even when the direct timeline is hard to crawl. - DeepSeek's official API quick-start still warns that
deepseek-chatanddeepseek-reasonerwill be deprecated on July 24, 2026 at 15:59 UTC. - DeepSeek's official change log repeats the same retirement date and clarifies the transition mapping:
deepseek-chatcurrently points to V4 Flash non-thinking mode, anddeepseek-reasonercurrently points to V4 Flash thinking mode. - The same official change log keeps
deepseek-v4-proanddeepseek-v4-flashas the current explicit model names, which makes alias cleanup a real operations task rather than a cosmetic docs update. - This is migration and support coverage only. It does not create any new plan card, stock promise, or pricing-page inventory change in this repo.
Why this is publishable
This is a current first-party support warning from official DeepSeek sources, not a community interpretation.
- It answers a time-sensitive production question: whether teams still have room to ignore old DeepSeek alias names.
- It stays inside official facts and does not invent any new roadmap or availability claim.
- It is distinct from the existing retirement-date guide coverage because today's news angle is not 'what migration looks like in general' but 'the warning is still live and the cutoff is now close enough to matter operationally.'
- It gives today's two new inner pages a tight official-source cluster instead of forcing another pricing or X recap into the news slot.
Rejected candidates today
- Direct official X timeline as the primary source: rejected because the timeline remained unreadable here even though DeepSeek's homepage still linked the official account.
- The homepage V4 Preview anchor itself: official, but older and already covered repeatedly in previous launch stories.
- The official status page: checked and healthy, but not stronger than the retirement warning for today's single news slot.
- Official GitHub and Hugging Face surfaces: checked as backup official sources, but neither exposed a clearer current DeepSeek API support headline than the docs-backed retirement warning.
Editorial takeaway
The clearest current DeepSeek developer signal is not a new launch post. It is a still-active official migration warning: teams relying on deepseek-chat or deepseek-reasoner are already on a compatibility bridge, and the official cutoff remains July 24, 2026. That is publish-safe, actionable, and stronger than recycling another older V4 preview mention.