Unconfirmed. An X post by @ZeroZ_JQ on Oct 28 highlighted deepseek-v5, deepseek-v5-open, and deepseek-v5-next strings in deepseek-ai/deepseek-harness provider.spec.ts and framed them as a near launch. @aitrackerbot replied that the linked file feeds V5-named entries into a local mock server for client-compatibility tests, including a dummy minimum version 99.0.0-alpha.1, and that the fixtures do not confirm a V5 model or an upcoming launch. The GitHub test itself asserts MODEL_UNSUPPORTED / CLIENT_UPGRADE_REQUIRED behavior against those fixture ids. DeepSeek has not announced V5. Kept Unconfirmed (not Debunked) per product stamp; not added to the daily brief.
Unit test 'hides and refuses listed models this build cannot serve' injects mock /models rows deepseek-v5, deepseek-v5-open (requires 0.0.1), and deepseek-v5-next (requires 99.0.0-alpha.1), then expects MODEL_UNSUPPORTED / CLIENT_UPGRADE_REQUIRED. Confirms the strings exist as fixtures, not a product announcement.
Quotes the ZeroZ post and clarifies that the linked file feeds V5-named entries into a local mock server to test client compatibility, including a dummy minimum version of 99.0.0-alpha.1; calls them test fixtures that do not confirm a V5 model or launch.
Says DeepSeek is about to ship a big update and that V5, V5-open, and V5-next already appear in the latest deepseek-harness code, linking provider.spec.ts#L154 with a screenshot. Not an official DeepSeek announcement.
We record what sources show, with dates. We don't predict or score how likely a rumor is.