skills.rest
danielbere1973
danielbere1973COMMUNITY
Explore all skills by this author →
GitHub

update-version

Updates AvailableFrom version tags in Remotion docs PRs to the next patch version.

Updated May 15, 2026
Search Tags:#git#versioning#documentation#pull request#release#remotion#patch version
One-click install
npx skills add https://github.com/danielbere1973/promoar --skill update-version-danielbere1973
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-version
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/update-version
Command: npx skills add https://github.com/danielbere1973/promoar --skill update-version-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a pull request adds documentation with <AvailableFrom v="..."> tags, the version value must match the next Remotion release. Manually computing the next patch version from main and finding every changed tag is error-prone and repetitive. ## Core Features & Use Cases - Canonical Version Lookup: Reads VERSION from packages/core/src/version.ts on origin/main and computes the next patch version. - PR-Scoped Updates: Uses git diff origin/main...HEAD to find only the AvailableFrom entries changed in the current PR, leaving unrelated values untouched. - Use Case: You open a PR documenting a new Remotion feature with <AvailableFrom v="4.0.468">. This Skill detects the current version is 4.0.468, computes 4.0.469, updates only your PR's tags, and commits the change. ## Quick Start Update the AvailableFrom versions in my current docs PR to the next Remotion patch version.

Frequently Asked Questions about update-version

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

FAQPage Schema
How do I update AvailableFrom versions in a Remotion docs PR?▼

Fetch origin/main, read VERSION from packages/core/src/version.ts, increment the patch number by one, then diff your PR against origin/main to find changed AvailableFrom entries and set them to the computed next version.

How is the next Remotion patch version calculated?▼

The canonical version is read from packages/core/src/version.ts on origin/main, for example 4.0.468. The next patch version increments the last number by one, producing 4.0.469.

Does this update all AvailableFrom tags in the docs?▼

No. Only AvailableFrom values changed within the current PR diff are updated. Entries outside the PR diff are explicitly left unchanged to avoid unrelated modifications.

What git commands find AvailableFrom entries changed in a PR?▼

Run git --no-pager diff origin/main...HEAD -- packages/docs piped to rg 'AvailableFrom v="' to list only the AvailableFrom lines touched by the current pull request.

When should AvailableFrom versions be updated in a PR?▼

Update them when a PR contains docs changes with AvailableFrom tags whose value should reflect the next release version rather than the current version on main.

Related Skills

Explore More Software Engineering Skills→
kbukumkbukum

create-branch

Creates git branches from up-to-date origin/main with reviewer-friendly naming conventions.

Community
Basic
ant-designant-design
99.3k

antd-version-release

Prepare release PRs and publish npm versions for the ant-design repository.

Official
Intermediate
zinohomezinohome
1

changelog-writer

Generate changelogs and release notes from git commits, PR titles, and issue references.

Community
Intermediate
remotion-devremotion-dev
57.9k

update-version

Update AvailableFrom version tags in Remotion documentation PRs to the next patch release.

Official
Basic