mcpField
R
remotion-upgrade

remotion-upgrade

github.com/remotion-devDevelopment5.8k206.8k installsUpdated 2d ago
Repository

About remotion-upgrade

A skill for upgrading Remotion in an existing project. It checks the package setup, aligns Remotion and auxiliary package versions, updates the lockfile, and reviews the resulting changes.

Key features

  1. 01Detects package manager and workspaces
  2. 02Uses the Remotion CLI when available
  3. 03Aligns Remotion package versions
  4. 04Updates auxiliary dependencies and lockfile
  5. 05Reviews upgrade diffs and versions

Use cases

  1. 01Upgrading an existing Remotion project
  2. 02Keeping Remotion packages on one version
  3. 03Updating Remotion skills alongside packages

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/remotion-dev/skills --skill remotion-upgrade

After installing, type/remotion-upgradein Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlassets/remotion-icon.svg

Details

From the project README

Upgrade Remotion

  1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.

  2. 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.

  3. 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 @remotion/studio dependencies for the target Remotion version using npm view @remotion/studio@<version> dependencies --json. Align installed auxiliary packages such as zod, mediabunny, and @huggingface/transformers with the versions listed there. Use the mediabunny version for installed @mediabunny/* packages.
    • Run the project's package manager to update its lockfile.

  4. 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-studio remotion-upgrade --yes

  5. Review the manifest and lockfile diff. Ensure all Remotion packages use one version and installed auxiliary packages use their recommended versions. 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.

Comments

Markdown supported