Backport: feat (video): add first-class frameImages and inputReferences call options for video generation - #16503
Merged
Conversation
shaper
approved these changes
Jun 30, 2026
joshualipman123
force-pushed
the
backport-pr-16219-to-release-v6.0
branch
from
June 30, 2026 07:16
585b060 to
63a6551
Compare
Contributor
|
🚀 Published in:
|
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.
Backport of #16219 to
release-v6.0.Summary
Promotes two image inputs to first-class top-level options on
experimental_generateVideo, instead of requiring provider-specific passthrough:frameImages— role-tagged images (first_frame/last_frame) for image-to-video and first-last-frame generation.inputReferences— reference images for reference-to-video (r2v) generation.Both are normalized once in core and passed through to providers, with warnings when they conflict (e.g.
frameImages+inputReferencessupplied together, or afirst_frameoverridingprompt.image).Backport notes
release-v6.0is on the VideoModelV3 spec, whereas the original PR targeted VideoModelV4 onmain. Adaptations:frameImages/inputReferencesto the v3 call-options type and a newvideo-model-v3-frame-image.ts(frame-image / frame-type definitions). All v4-only files from the PR were dropped (v4call-options,v4frame-image,as-video-model-v4.test.ts).generate-video.tskeeps the v3satisfies Experimental_VideoModelV3CallOptionsshape; allVideoModelV4*types swapped to theirV3equivalents.normalizeImageDatato v6.0'sdetectMediaType({ signatures: imageMediaTypeSignatures })API (the PR used main-only{ topLevelType: 'image' }).specificationVersion = 'v3'withVideoModelV4→VideoModelV3renames throughout.google-generative-ai-video-model.tskeeps v6.0's class nameGoogleGenerativeAIVideoModel(renamed toGoogleVideoModelon main).google-vertex-video-model.tskeeps v6.0'svertexOptionsvariable name (renamed togoogleVertexOptionson main).vertex(the PR used the main-onlygoogleVertex).