| name | release-tag |
| description | Tag a prepared leather release and push the tag to origin. Triggers the automated release pipeline. USE FOR: after release-prep has committed and pushed. DO NOT USE FOR: preparing the CHANGELOG or docs (use release-prep first); creating GitHub releases directly (the pipeline handles that). |
| compatibility | Designed for Claude Code and similar coding agents working in the leather repository. |
| metadata | {"argument-hint":"Version to tag, e.g. \"v0.1.3\". Must match the CHANGELOG entry created by leather-release-prep.","user-invocable":"true"} |
leather-release-tag
Creates and pushes an annotated git tag for a prepared leather release.
The automated pipeline (GitHub Actions) fires on tag push and creates the
GitHub release — do not call gh release create manually.
Run leather-release-prep first to ensure the working tree and CHANGELOG
are ready.
Pre-flight gates (all four must pass)
Gate 1 — Clean working tree
git status --porcelain
Must return empty output. If not, abort: "working tree is dirty — commit or
stash changes before tagging."
Gate 2 — In sync with origin/main
git fetch origin main
git rev-list HEAD..origin/main --count
Must return 0. If not, abort: "local main is behind origin — pull before
tagging."
Gate 3 — CHANGELOG has the version
grep -F "## [VERSION]" CHANGELOG.md
Must find at least one match. If not, abort: "CHANGELOG.md has no section for
VERSION — run leather-release-prep first."
Gate 4 — Tag does not already exist
git tag --list VERSION
Must return empty. If not, abort: "tag VERSION already exists locally or on
origin."
Tag and push
All four gates passed — proceed:
git tag -a VERSION -m "VERSION"
git push origin VERSION
Verify
Confirm the tag landed on origin:
git ls-remote origin refs/tags/VERSION
Must return a non-empty line. If empty, the push silently failed — retry the
push or investigate git remote -v.
What happens next
The .github/workflows/release.yml pipeline fires on the tag push. It:
- Builds the static binary for each target platform.
- Creates the GitHub release with the CHANGELOG section for this version as
the body.
- Attaches the binaries as release assets.
Do not create the GitHub release manually. Do not re-push the tag. Monitor
the Actions tab if the pipeline does not appear within ~30 seconds of the push.
Checklist
