Update release availability labels in Remotion documentation changed by a pull request. Read the version on main, increase its patch number by one, and update only the affected labels before committing and pushing.
Update `AvailableFrom` in a PR to the next Remotion patch version (`main` + `0.0.1`).
Review the instructions the agent will receive before you install.
Use this when a PR contains docs changes with <AvailableFrom v="..."> and the value should reflect the next release version.
main:git fetch origin main --quiet
git --no-pager show origin/main:packages/core/src/version.ts
Read VERSION from that file (for example: 4.0.468), then compute the next patch version by incrementing the patch number by 1 (4.0.469).
AvailableFrom entries changed in the current PR:git --no-pager diff origin/main...HEAD -- packages/docs | rg 'AvailableFrom v="'
Update only AvailableFrom values touched by this PR so they match the computed next patch version from step 1.
Do not change unrelated AvailableFrom values outside the PR diff.
Commit and push the update.
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.