$npx -y skills add remotion-dev/remotion --skill remotion-upgradeUpgrade Remotion, its related packages, compatible Mediabunny packages, and installed Remotion Agent Skills. Use when asked to upgrade or update a Remotion project.
| 1 | # Upgrade Remotion |
| 2 | |
| 3 | 1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes. |
| 4 | 2. Determine whether `@remotion/cli` is locally available. If it is, run: |
| 5 | |
| 6 | ```bash |
| 7 | npx remotion upgrade |
| 8 | ``` |
| 9 | |
| 10 | Skip the manual package upgrade below. |
| 11 | |
| 12 | 3. If `@remotion/cli` is not available, upgrade manually: |
| 13 | - Get the latest stable Remotion version with `npm view remotion version`. |
| 14 | - 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. |
| 15 | - Read the current [Mediabunny compatibility page](https://www.remotion.dev/docs/mediabunny/version) and determine the Mediabunny version compatible with the target Remotion version. Upgrade every installed `mediabunny` and `@mediabunny/*` package to the documented compatible version. |
| 16 | - Run the project's package manager to update its lockfile. |
| 17 | 4. Update the installed Remotion skills: |
| 18 | |
| 19 | ```bash |
| 20 | npx remotion skills update |
| 21 | ``` |
| 22 | |
| 23 | 5. 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. |
| 24 | |
| 25 | The [Remotion releases](https://github.com/remotion-dev/remotion/releases) contain the changelog and may be useful for summarizing relevant changes after the upgrade. |