[Fix] Images rejected as unsupported when using DeepSeek V4 Pro or V4 Flash#969
Closed
zoomote[bot] wants to merge 1 commit into
Closed
[Fix] Images rejected as unsupported when using DeepSeek V4 Pro or V4 Flash#969zoomote[bot] wants to merge 1 commit into
zoomote[bot] wants to merge 1 commit into
Conversation
Contributor
Author
This was referenced Jul 21, 2026
Contributor
Author
|
Closing as duplicate of #963, which was already open for the same fix. The paired docs PR (Zoo-Code-Docs#15) remains open. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related GitHub Issue
Closes: #964
Description
DeepSeek V4 Pro and V4 Flash were marked
supportsImages: falseinpackages/types/src/providers/deepseek.ts, so image attachments were blocked withunsupported_modeleven though the DeepSeek API accepts image inputs. This PR flipssupportsImagestotruefordeepseek-v4-proanddeepseek-v4-flashonly; the legacydeepseek-chatanddeepseek-reasoneraliases keepsupportsImages: falseas they do not support vision and are being retired. The image transport path already handles these models:convertToR1Formatconverts base64 image blocks to OpenAIimage_urlcontent parts, so no pipeline changes were needed. Regression assertions were added todeepseek.spec.tscoveringsupportsImagesfor both V4 models (the legacy aliases were already asserted asfalse).Test Procedure
pnpm testpasses (10/10 turbo tasks), including the updatedsrc/api/providers/__tests__/deepseek.spec.tsassertions that both V4 models reportsupportsImages: trueand both legacy aliases still reportfalse.deepseek-v4-proordeepseek-v4-flashand attaching an image; it should no longer be rejected withunsupported_model.Pre-Submission Checklist
Screenshots / Videos
Not applicable — this is a model metadata flag change with no UI rendering change.
Documentation Updates
Additional Notes
Related PRs
Linked work items
Closes #964
Get in Touch
Available via this PR's comments for any reviewer questions.