fix: update @shotstack/schemas to 1.14.0 and handle srcless generated assets#138
Merged
Conversation
This was referenced Jul 13, 2026
|
🎉 This PR is included in version 2.13.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
1 participant
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.
What changed
The schemas dependency was pinned to 1.11.0, so the editor validated edits against a contract several versions behind the render API. Templates using newer API features — the
newscastervoice option on audio assets, prompt-driven audio (prompt/voice/model) — failed strict validation at load and could not be opened in the editor, even though they render fine via the API.@shotstack/schemas1.11.0 → 1.14.0 so load-time validation matches the current API contract.srcoptional on audio, image, and video assets (generation-driven assets have no source until generated). Players and the thumbnail renderer now throw a clear per-clip error for a srcless asset instead of failing onundefined— clip load failures are already caught per clip, so the edit still opens with the affected clip flagged.How to verify
New tests in
tests/schema.test.ts("API-accepted templates parse at load"): text-to-speech and prompt-driven audio assets withnewscasterparse successfully (the audio case fails on 1.11.0), and a destination without an options object is accepted. Full suite passes (1847 tests), tsc and lint clean, build succeeds.