Update to Remotion
Snapshot Oct 2, 2026 · 00:37 UTC · version 4.0.530
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for remotion-upgrade
Instruction wording changed from “4.0.506” to “4.0.530”. 2 additional added or edited lines are in the evidence.
Observed in instructions or declared skills. Runtime behavior has not been tested.
Skill instructions
4.0.506 - 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 `@...
4.0.530 - 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/tran...
Supporting files
[{"relative_path":"agents/openai.yaml","size_in_bytes":282},{"relative_path":"assets/remotion-icon.png","size_in_bytes":1286}]
[{"relative_path":"agents/openai.yaml","size_in_bytes":282},{"relative_path":"assets/remotion-icon.svg","size_in_bytes":1303}]
Compare saved observations
Download comparison JSONFull technical diff · 2 changed fields
changed /included_files
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 282
},
{
"relative_path": "assets/remotion-icon.png",
"size_in_bytes": 1286
}
][
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 282
},
{
"relative_path": "assets/remotion-icon.svg",
"size_in_bytes": 1303
}
]changed /skill_md_contents
"---\nname: remotion-upgrade\ndescription: Upgrade Remotion, and related packages\nversion: 4.0.506\n---\n\n# Upgrade Remotion\n\n1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.\n2. Determine whether `@remotion/cli` is locally available. If it is, run:\n\n ```bash\n npx remotion upgrade\n ```\n\n This also updates project-local Remotion skills. Skip the manual upgrade below.\n\n3. If `@remotion/cli` is not available, upgrade manually:\n - Get the latest stable Remotion version with `npm view remotion version`.\n - 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.\n - 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.\n - Run the project's package manager to update its lockfile.\n4. If `@remotion/cli` is not available, update the installed Remotion skills:\n\n ```bash\n 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\n ```\n\n5. 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.\n\nThe [Remotion releases](https://github.com/remotion-dev/remotion/releases) contain the changelog and may be useful for summarizing relevant changes after the upgrade.\n"
"---\nname: remotion-upgrade\ndescription: Upgrade Remotion, and related packages\nversion: 4.0.530\n---\n\n# Upgrade Remotion\n\n1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.\n2. Determine whether `@remotion/cli` is locally available. If it is, run:\n\n ```bash\n npx remotion upgrade\n ```\n\n This also updates project-local Remotion skills. Skip the manual upgrade below.\n\n3. If `@remotion/cli` is not available, upgrade manually:\n - Get the latest stable Remotion version with `npm view remotion version`.\n - 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.\n - 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.\n - Run the project's package manager to update its lockfile.\n4. If `@remotion/cli` is not available, update the installed Remotion skills:\n\n ```bash\n 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\n ```\n\n5. 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.\n\nThe [Remotion releases](https://github.com/remotion-dev/remotion/releases) contain the changelog and may be useful for summarizing relevant changes after the upgrade.\n"
SKILL.md line diff
--- before +++ after @@ -1,7 +1,7 @@ --- name: remotion-upgrade description: Upgrade Remotion, and related packages -version: 4.0.506 +version: 4.0.530 --- # Upgrade Remotion @@ -18,7 +18,7 @@ 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 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. + - 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: @@ -26,6 +26,6 @@ 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 all installed Mediabunny packages use the compatible version. If the CLI is available, run `npx remotion versions` as an additional check. +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](https://github.com/remotion-dev/remotion/releases) contain the changelog and may be useful for summarizing relevant changes after the upgrade.
Full snapshot data
{
"description": "Upgrade Remotion, and related packages",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 282
},
{
"relative_path": "assets/remotion-icon.svg",
"size_in_bytes": 1303
}
],
"name": "remotion-upgrade",
"skill_md_contents": "---\nname: remotion-upgrade\ndescription: Upgrade Remotion, and related packages\nversion: 4.0.530\n---\n\n# Upgrade Remotion\n\n1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.\n2. Determine whether `@remotion/cli` is locally available. If it is, run:\n\n ```bash\n npx remotion upgrade\n ```\n\n This also updates project-local Remotion skills. Skip the manual upgrade below.\n\n3. If `@remotion/cli` is not available, upgrade manually:\n - Get the latest stable Remotion version with `npm view remotion version`.\n - 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.\n - 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.\n - Run the project's package manager to update its lockfile.\n4. If `@remotion/cli` is not available, update the installed Remotion skills:\n\n ```bash\n 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\n ```\n\n5. 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.\n\nThe [Remotion releases](https://github.com/remotion-dev/remotion/releases) contain the changelog and may be useful for summarizing relevant changes after the upgrade.\n"
}SHA-256 of public snapshot: 671b6897a6c32a847f721be9c0b882b7a87fa026f74e778ab17981f2cf7e0990