Menü
Use after a release branch has been merged into main - fetches latest main, creates an annotated git tag, and pushes it to trigger the release workflow.
Use when preparing a release branch - version bump, CHANGELOG update, build verification, and commit. Stops after commit and asks user to merge the branch.
Use when performing a release to automate the full release flow - versioning, CHANGELOG update, git tagging, and deploy trigger via push.
| name | release-tag |
| description | Use after a release branch has been merged into main - fetches latest main, creates an annotated git tag, and pushes it to trigger the release workflow. |
Completes the release by fetching the latest main, creating an annotated git tag, and pushing it to trigger the .github/workflows/release.yml deploy pipeline.
Run this after the release branch has been merged into main (i.e., after /release-branch completes and the merge is confirmed).
git checkout main
git pull origin main
Read the current version from package.json:
node -p "require('./package.json').version"
# Example output: 2.5.0
NEW_VERSION=<version>
git tag -a v<NEW_VERSION> -m "Release v<NEW_VERSION>"
git push origin v<NEW_VERSION>
Pushing the tag triggers the .github/workflows/release.yml workflow which runs the full release pipeline (build, publish).
v prefix (e.g., v2.5.0).main branch only.npm publish is applicable for this project, the .github/workflows/release.yml workflow handles it automatically on tag push.