Remotion Upgrade

Upgrade Remotion

• Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.
• Determine whether @remotion/cli is locally available. If it is, run:

   npx remotion upgrade

This also updates project-local Remotion skills. Skip the manual upgrade below.

• If @remotion/cli is not available, upgrade manually:
• Get the latest stable Remotion version with npm view remotion version.
• Find every installed remotion and @remotion/* dependency across the project and upgrade them all to that exact version. Preserve their dependency sections and the project's workspace or catalog conventions.
• Read the current Mediabunny compatibility page and determine the Mediabunny version compatible with the target Remotion version. Upgrade every installed mediabunny and @mediabunny/* package to the documented compatible version.
• Run the project's package manager to update its lockfile.
• If @remotion/cli is not available, update the installed Remotion skills:

   npx skills update remotion-best-practices remotion-captions remotion-create remotion-docs remotion-interactivity remotion-maps remotion-markup remotion-multimedia remotion-render remotion-saas remotion-upgrade --yes

• Review the manifest and lockfile diff. Ensure all Remotion packages use one version and all installed Mediabunny packages use the compatible version. If the CLI is available, run npx remotion versions as an additional check.

The Remotion releases contain the changelog and may be useful for summarizing relevant changes after the upgrade.