chore(deploy): switch the platform AI to DeepSeek deepseek-flash
Point ai.baseUrl at https://api.deepseek.com and ai.model at
deepseek-flash; the key moves in PROD_SECRET_VALUES (APP_AI__API_KEY),
which is why nothing here carries it.
Probed the endpoint before switching: /models lists deepseek-flash as
DeepSeek-V4.1-Flash (1M context, image input, effort levels low/high/max),
/chat/completions accepts our exact body shape including the aliyun-era
thinking_budget field, JSON mode returns the {content,highlights,risks}
shape we parse, and the chain of thought arrives in reasoning_content
exactly as the client already expects. Small structured tasks come back in
1.5-3.0s where the previous qwen3.8-flash took 42-77s, so the 600s request
timeout and the 2048 thinking budget stay as they are.
Only configuration changed - the image stays sha-6d1afbc; the rollout that
follows is the env change restarting the pods.
ZhenYi committed
Modified deploy/values/prod.yaml deploy/values/prod.yaml +7 −2 View deploy/values/prod.yaml
@@ -190,12 +190,17 @@
190190
191191# ---------------------------------------------------------------------------
192192# AI:评审 / 仓库总结 / release 文案(值对齐 config/local.toml)
193# 供应商:DeepSeek(https://api.deepseek.com,OpenAI 兼容)。
193194# api_key 走 secret.env -> APP_AI__API_KEY
195# 端点探测(2026-09-29):/models 返回 deepseek-flash = DeepSeek-V4.1-Flash,
196# 1M 上下文、支持结构化 JSON(response_format=json_object)且会把思维链单独放在
197# reasoning_content;小任务 1.5-3.0s 返回,比之前的 aliyun MaaS qwen3.8-flash
198# 快一个数量级。thinking_budget 该端点接受(不报错),故保持 2048 不变。
194199# ---------------------------------------------------------------------------
195200ai:
196201 enabled: true
197 baseUrl: "https://llm-g0x83i22nyj4pub7.cn-beijing.maas.aliyuncs.com/compatible-mode/v1"
198 model: "qwen3.8-flash"
202 baseUrl: "https://api.deepseek.com"
203 model: "deepseek-flash"
199204 reviewEnabled: true
200205 summaryEnabled: true
201206 releaseNotesEnabled: true