skills.rest
remotion-dev
remotion-devOFFICIAL
Explore all skills by this author →
Website𝕏@remotionGitHub

upgrade-mediabunny

Upgrade Mediabunny packages across the Remotion monorepo to the latest version.

57.9k|4.4k|Updated Jun 23, 2020
Search Tags:#package.json#Bun#Monorepo#version management#dependency upgrade#Remotion#mediabunny
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill upgrade-mediabunny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrade-mediabunny
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/upgrade-mediabunny
Command: npx skills add https://github.com/remotion-dev/remotion --skill upgrade-mediabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Mediabunny and its related packages in sync across a large monorepo is error-prone, with version strings scattered across root catalogs, templates, CLI configs, and documentation. This Skill automates the coordinated update so every reference moves to the same release.

Core Features & Use Cases

  • Catalog and Template Synchronization: Updates the root package.json catalog entries and every packages/template-*/package.json to the latest Mediabunny version.
  • Internal Config Updates: Refreshes version references in packages/cli/src/extra-packages.ts and packages/studio-shared/src/package-info.ts.
  • Documentation Alignment: Updates the compatibility table in packages/docs/docs/mediabunny/version.mdx to reflect the new release.
  • Use Case: When a new Mediabunny release ships, run this Skill to bump every dependency, config file, and doc reference in the Remotion repo in one pass.

Quick Start

Upgrade Mediabunny to the latest version across the Remotion repository.

Frequently Asked Questions about upgrade-mediabunny

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Mediabunny to the latest version in the Remotion repo?▼

Run the upgrade-mediabunny skill, which queries `npm view mediabunny version` for the latest release, then updates the root catalog, all template package.json files, CLI and studio-shared configs, and the docs compatibility table before running `bun i`.

What Mediabunny packages need to be updated together?▼

The core `mediabunny` package plus `@mediabunny/mp3-encoder` and `@mediabunny/ac3` must be kept in sync. Templates use explicit version strings rather than the catalog reference, so each template package.json must be updated manually.

Does the Remotion monorepo use a catalog for Mediabunny dependencies?▼

Yes, the root `package.json` defines a `catalog` entry for Mediabunny packages. Templates do not use the catalog and instead pin explicit versions, which the upgrade process updates directly.

Where is the Mediabunny compatibility table located?▼

The compatibility table lives in `packages/docs/docs/mediabunny/version.mdx`. The next Remotion version to apply the upgrade is derived from the root `package.json` version with the patch segment incremented by one.

Why do template package.json files need manual version updates?▼

Templates pin explicit Mediabunny versions instead of referencing the workspace catalog. This ensures published templates remain reproducible, but it means each template must be updated individually during an upgrade.

Related Skills

Explore More Software Engineering Skills→
helderbertohelderberto
12

deps-audit

Audit npm dependencies for vulnerabilities and outdated packages.

Community
Intermediate
tachiiri-orgtachiiri-org

deploy-electron

Package and publish Electron applications to GitHub Releases with branch-aware prerelease handling.

Official
Advanced
LynxLabVNLynxLabVN

ascii-video

Convert video, audio, and image content into ASCII art animations using ffmpeg and Python libraries.

Official
Advanced
as4584as4584
2

dependency-upgrade

Manage major dependency upgrades with compatibility analysis and staged rollouts.

Community
Advanced