Repository navigation
fix: use supported Studio Ghibli version in Node example - #580
Merged
Merged
Conversation
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
2 participants
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.
Select the supported
v2configuration in the Node Video-to-Video guide's Studio Ghibli example. The current default resolves to a v3 model that REST explicitly rejects before creating a project; no runtime, pricing or model-availability changes.Validation: current REST/template and Node serializer review, independent exact-diff review, changed-file Prettier, Mintlify broken-links and whitespace checks passed. Three table-padding lines normalized by the required formatter. No paid generation performed.