update-version

toolingremotion-dev

Update `AvailableFrom` in a PR to the next Remotion patch version (`main` + `0.0.1`).

Install

npx skills add https://github.com/remotion-dev/remotion --skill update-version

SKILL.md

---name: update-versiondescription: Update `AvailableFrom` in a PR to the next Remotion patch version (`main` + `0.0.1`).---

Use this when a PR contains docs changes with <AvailableFrom v="..."> and the value should reflect the next release version.

Get the canonical version from 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).

Find 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.

Related skills

setup-matt-pocock-skillsmattpocock905KConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.hyperframes-cliheygen-com714KUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, history, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers lo implementmattpocock627KImplement a piece of work based on a spec or set of tickets.ask-mattmattpocock626KAsk which skill or flow fits your situation. A router over the skills in this repo.