Skip to content
Source
Sign inSign up
TanStack/schemas

lovable spec sync fails: video schema still mentions Sora after the #666 rewrite #680

Send to my agent
Closedtombeckenham opened this issue 0 comments
tombeckenhamcommented

What fails

The first daily spec sync after #666 deployed (2026-11-16 21:33 UTC) failed for lovable on 2026-11-17 05:20 UTC (PostHog ingest_failed, job spec-sync):

lovable: video schema still mentions Sora

It will fail on every daily run, so Lovable's video endpoint keeps the stored schema, which #659 reported as copied from OpenAI Sora.

Cause

src/server/providers/lovable-video.ts:270-285 rewrites the OpenAI-based video schemas (CreateVideoMultipartBody, CreateVideoJsonBody, the branches, VideoModel, VideoSeconds, VideoSize) and then throws if the JSON still matches /sora/i. Something in the live OpenAI spec that the rewrite doesn't replace still says Sora: most likely a description, an example, or a $ref/enum value that the #666 test fixture doesn't have.

Fix

  • Reproduce against the live OpenAI spec (the same input the sync uses), and find which key and path still contain "sora".
  • Rewrite or drop that text the same way #666 handles the rest, from Lovable's own page (https://docs.lovable.dev/features/ai-video). Never copy a Sora value in.
  • Keep the guard. Make its error name the JSON path that matched, so the next failure says where.
  • Add that live shape to the test fixture.
  1. tanstack-source added labelsbug

  2. tombeckenham linked this to #681

  3. tombeckenham closed this

Sign in to join this conversation.