Update FFmpeg archives in a Remotion monorepo after the seven platform builds complete. The workflow imports verified artifacts, regenerates bindings, rebuilds compositor binaries, and checks the resulting changes and pull request.
Update the monorepo FFmpeg archives, regenerate bindings, rebuild compositor binaries, and validate a single Remotion pull request. Use after the seven-platform FFmpeg build completes.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The FFmpeg build recipes, Rust bindings and wrapper live in packages/compositor/ffmpeg. The compositor and wrapper use local Cargo dependencies, and updates are reviewed in a single Remotion pull request.
Use the full source commit SHA for the intended FFmpeg build.
Explicitly trigger the CircleCI pipeline on the branch containing that commit using the web app's Trigger Pipeline button or the API. No parameters are needed: the workflow only runs for pipeline.trigger.type == "api", which covers both methods. See the trigger instructions. Wait for its five jobs and the macOS GitHub Actions build for the same commit to succeed. Then collect artifacts from the Remotion repository root:
node packages/compositor/ffmpeg/collect-artifacts.mjs --sha <full-source-sha>
The collector requires successful GitHub Actions and CircleCI builds for that same SHA. Do not combine runs or fill missing targets from an older build. Keep the returned MANIFEST.json and SHA256SUMS with the seven archives.
Upload the verified archives to a new immutable directory on remotion.media using the repository's R2 upload workflow. Never overwrite an existing release directory. Then run:
node packages/compositor/ffmpeg/import-artifacts.mjs <artifact-directory> <immutable-https-base-url>
The importer verifies local and hosted archive checksums before updating assets.json and the seven canonical generated bindings. Archives remain ignored downloads. Do not hand-edit bindings.
Install dependencies with bun install --frozen-lockfile. From packages/compositor, install missing cross-compilation toolchains with bun install-toolchain.ts, then run bun run build-all.
Require all seven targets: Windows x64 GNU, macOS ARM64/x64, Linux ARM64/x64 GNU/musl. On macOS, use an MSVCRT-targeting x86_64-w64-mingw32-gcc. Verify objdump -p packages/compositor-win32-x64-msvc/remotion.exe imports msvcrt.dll and no api-ms-win-crt-* or ucrtbase.dll.
From the repository root, run bun run build, bun run stylecheck, and git diff --check. Inspect the FFmpeg metadata/binding changes and all seven rebuilt compositor packages. Do not include unrelated changes.
When a PR is requested, read ../pr/SKILL.md and ../pr-name/SKILL.md. Include the full source SHA, hosted archive directory, CI provenance, rebuilt targets and validation results. Use the title:
`@remotion/compositor`: Update FFmpeg and rebuild binaries
packages/lambda-binaries packages Chromium and fonts and does not need a rebuild for an FFmpeg-only update.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.