update-remotion-rust-ffmpeg

Update ffmpeg-next revision, rebuild compositor binaries, and open a draft pull request.

57.9k|4.4k|Updated Jun 23, 2020
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill update-remotion-rust-ffmpeg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-remotion-rust-ffmpeg
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/update-remotion-rust-ffmpeg
Command: npx skills add https://github.com/remotion-dev/remotion --skill update-remotion-rust-ffmpeg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Remotion's compositor binaries in sync with upstream rust-ffmpeg releases requires coordinated Cargo updates, cross-platform rebuilds, and careful PR hygiene. This Skill automates the final step of that multi-repository chain so the dependency bump lands cleanly.

Core Features & Use Cases

  • Cargo Lockfile Refresh: Updates ffmpeg-next.rev in packages/compositor/Cargo.toml and verifies ffmpeg-sys-next resolves to the matching rust-ffmpeg-sys SHA.
  • Cross-Platform Rebuild: Builds compositor binaries for Windows x64 GNU, macOS ARM64/x64, and Linux ARM64/x64 GNU/musl, including MSVCRT validation on Windows.
  • Draft PR Creation: Stages only the intended files, commits with a fixed title, pushes once, and opens a draft PR against main with a structured body.

Quick Start

Run the update-remotion-rust-ffmpeg skill with the merged rust-ffmpeg commit hash to rebuild all compositor targets and open a draft pull request.

Frequently Asked Questions about update-remotion-rust-ffmpeg

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update ffmpeg-next in the Remotion compositor package?

Change `ffmpeg-next.rev` in `packages/compositor/Cargo.toml` to the supplied rust-ffmpeg SHA, then run `cargo update -p ffmpeg-next` from that directory. Verify `Cargo.lock` resolves both `ffmpeg-next` and `ffmpeg-sys-next` to the expected SHAs.

What platforms does the Remotion compositor build target?

The build covers Windows x64 GNU, macOS ARM64 and x64, and Linux ARM64 and x64 in both GNU and musl variants. On macOS, an MSVCRT-targeting `x86_64-w64-mingw32-gcc` linker is required for the Windows target.

Why does the Windows compositor build require MSVCRT instead of UCRT?

The skill rejects `api-ms-win-crt-*` and `ucrtbase.dll` imports via `objdump -p` on `remotion.exe`. Only `msvcrt.dll` is accepted, so a UCRT-defaulting mingw toolchain will fail validation.

Can I force-push or rebase the update branch?

No. The skill explicitly forbids force-push, rebase, reset, and overwriting unrelated work. If `git push -u origin HEAD` is rejected, the workflow stops and reports the conflict instead of retrying.

What files should be staged for the update commit?

Stage only the two Cargo files, the seven rebuilt compositor platform packages, `packages/compositor/build.ts`, and any intentional update to the skill itself. Any unrelated tracked changes cause the workflow to stop.