← RemotionCONTENT HISTORY

Update to Remotion

Snapshot Oct 8, 2026 · 18:03 UTC · version 4.0.534

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

Instructions updated for remotion-upgrade

Instruction wording changed from “4.0.530” to “4.0.534”.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Short excerpts from up to four changed fields. Open the full comparison for all changes.

Skill instructions

Before

Oct 2, 2026 · 00:37 UTC

version: 4.0.530

After

Oct 8, 2026 · 18:03 UTC

version: 4.0.534

Compare saved observations

Download comparison JSON

SKILL.md text changes

Lines starting with − were removed; lines starting with + were added. Other lines provide context.

--- before
+++ after
@@ -1,7 +1,7 @@
 ---
 name: remotion-upgrade
 description: Upgrade Remotion, and related packages
-version: 4.0.530
+version: 4.0.534
 ---
 
 # Upgrade Remotion
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\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"
AFTER
"---\nname: remotion-upgrade\ndescription: Upgrade Remotion, and related packages\nversion: 4.0.534\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"
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.534\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: a07a4503620a32eac35f6316260f32f085038465f0c5b0ee0b8dd47f58a51067