update-version
Update `AvailableFrom` in a PR to the next Remotion patch version (`main` + `0.0.1`).
62
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/update-version/SKILL.mdUse 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.tsRead 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
AvailableFromentries changed in the current PR:
git --no-pager diff origin/main...HEAD -- packages/docs | rg 'AvailableFrom v="'-
Update only
AvailableFromvalues touched by this PR so they match the computed next patch version from step 1. -
Do not change unrelated
AvailableFromvalues outside the PR diff. -
Commit and push the update.
- Repository
- remotion-dev/remotion
- Commit
a2a8435
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.