Skip to content

docs: align with DeepSeek-V4-Pro GA (2026-08-12) - #1

Merged
lroolle merged 1 commit into
mainfrom
feat/v4-pro-ga
Aug 12, 2026
Merged

docs: align with DeepSeek-V4-Pro GA (2026-08-12)#1
lroolle merged 1 commit into
mainfrom
feat/v4-pro-ga

Conversation

@lroolle

@lroolle lroolle commented Aug 12, 2026

Copy link
Copy Markdown
Member

What

DeepSeek-V4-Pro went GA today (model version DeepSeek-V4-Pro-0813; model ID unchanged, rate card unchanged). The catalog numbers were already correct, so this is a docs/comment alignment only:

  • src/provider/catalog.ts — pricing provenance comment was stale: it described "off-peak" rates and a peak-hour 2x plan upstream has since dropped in favor of an undated overall repricing. Re-verified rates/context/max-output at GA; comment now warns not to bake in the repricing until it has an effective date.
  • README.md — mentions the GA (version 0813, same model ID), notes both models are selectable everywhere a model is chosen, and that pro is the stronger tier for planning/review (the built-in reviewer sub-agent role already runs on it). Calls out thinking-on-by-default and that reasoning tokens count against max_tokens — existing budget handling is untouched.

Not changed

  • No pricing edits (rates unchanged at GA; announced repricing is undated).
  • No default-model, max_tokens, or routing changes.

Test

bun test tests — 117 pass, 0 fail.

🤖 Generated with Claude Code

V4-Pro went GA today as model version DeepSeek-V4-Pro-0813; the model
ID stays deepseek-v4-pro and the rate card is unchanged, so the
catalog numbers were already correct. What was stale:

- catalog.ts provenance comment still described "off-peak" rates and a
  peak-hour 2x plan upstream has since dropped in favor of an undated
  overall repricing. Re-verified the rates at GA; the comment now says
  not to apply the repricing until it lands with an effective date.
- README never mentioned the GA. It now notes the GA version, that
  both models are selectable at every model-choice point, and that pro
  is the stronger tier for planning/review (the reviewer sub-agent
  role already runs on it). Thinking-on-by-default and the
  reasoning-tokens-count-against-max_tokens behavior are called out;
  no defaults were changed.

No runtime behavior changes. bun test tests: 117 pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lroolle
lroolle merged commit d5c95b5 into main Aug 12, 2026
1 check passed
@lroolle
lroolle deleted the feat/v4-pro-ga branch August 12, 2026 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant