Internal: Stabilize timing override registration test in @remotion/transitions

[samohovets]

Summary

• replace fixed 10ms sleeps in the TransitionSeries timing override test
• wait for both sequences and the transition to register after each render
• avoid scheduler-dependent failures on slower CI runners

Verification

• cd packages/transitions && bun test src/test/transition-series-stack.test.tsx --test-name-pattern "TransitionSeries.Sequence timing overrides cascade to later sequences" --rerun-each 100
• cd packages/transitions && bun test
• bun run build
• bun run stylecheck

Related to #8375.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Jul 27, 2026 5:13pm
remotion	Ready	Preview, Comment	Jul 27, 2026 5:13pm

[pullfrog]

✅ No new issues found.

Reviewed changes — replaces brittle setTimeout(10) sleeps in the timing-override registration test with an event-driven synchronization approach that waits for each sequence and transition to actually register, matching the same pattern already used in the TransitionSeries.Transition and Overlay register at their rendered timeline ranges test.

• Replace setTimeout sleeps with registration-completion promises — each renderTransitionSeries() call now resets a pendingRegistrationStacks set and returns a promise that resolves when all three stacks (first sequence, second sequence, transition) have been observed by onRegisterSequence.
• Convert all three call sites to await renderTransitionSeries(...) — removes the orphaned setTimeout lines and relies on the returned promise instead.

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (Claude Opus not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}