Update Mediabunny and its related packages throughout Remotion, including templates, CLI version references, and the documentation compatibility table. The workflow checks the latest published version, aligns the relevant entries, and finishes by installing dependencies with Bun.
Upgrade Mediabunny and related @mediabunny packages across the Remotion repo. Use when asked to update Mediabunny to the latest version.
Review the instructions the agent will receive before you install.
npm view mediabunny version.package.json, update the catalog versions for mediabunny, @mediabunny/mp3-encoder, and @mediabunny/ac3 to that version.packages/template-*/package.json, update mediabunny and any @mediabunny/* packages to the same version. Templates use explicit versions, not catalog:, so update them manually.packages/cli/src/extra-packages.ts with the new Mediabunny version.packages/studio-shared/src/package-info.ts with the new Mediabunny version in extraPackages.packages/docs/docs/mediabunny/version.mdx. To find the next version this upgrade will be applied to, look in the root package.json for the version and increment the patch version by 1.bun i at the end.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.