Skills

Skill 12 of 12

Remotion Upgrade

Upgrade Remotion, and related packages

1 minute · 175 words · 1 sections

Install

$ npx skills add remotion-dev/skills --skill remotion-upgrade

$ npx skills add remotion-dev/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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

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

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 (opens in a new tab) contain the changelog and may be useful for summarizing relevant changes after the upgrade.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/remotion-dev/skills, branch main, last pushed 24 September 2026.

Licence

Discovery

12 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from a curated brand profile — hue 254°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “1 heading” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /remotion-dev/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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

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

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.

Remotion Upgrade

Upgrade Remotion

Colophon

Remotion Upgrade

Upgrade Remotion

Appendix 12.1–12.2

AssetsSVG · 1 file

Also bundledYAML · 1 file

Colophon

Appendix 12.1–12.2

AssetsSVG · 1 file

Also bundledYAML · 1 file