releaselisted

Prepare and ship a term-mesh release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release.
x-mesh/term-mesh · ★ 0 · Code & Development · score 67

Install: claude install-skill x-mesh/term-mesh

# Release Run this workflow to prepare and publish a term-mesh release. ## Workflow 1. Determine the version: - Read `MARKETING_VERSION` from `GhosttyTabs.xcodeproj/project.pbxproj`. - Default to a minor bump unless the user explicitly requests patch/major/specific version. 2. Create a release branch: - `git checkout -b release/vX.Y.Z` 3. Gather user-facing changes and contributors since the last tag: - `git describe --tags --abbrev=0` - `git log --oneline <last-tag>..HEAD --no-merges` - Keep only end-user visible changes (features, bug fixes, UX/perf behavior). - **Collect contributors:** For each PR, get the author with `gh pr view <N> --repo x-mesh/term-mesh --json author --jq '.author.login'`. Also check linked issue reporters with `gh issue view <N> --json author --jq '.author.login'`. - Build a deduplicated list of all contributor `@handle`s. 4. Update changelogs: - Update `CHANGELOG.md`. - Update `docs-site/content/docs/changelog.mdx`. - Use categories `Added`, `Changed`, `Fixed`, `Removed`. - **Credit contributors inline** (see Contributor Credits below). - If no user-facing changes exist, confirm with the user before continuing. 5. Bump app version metadata: - Prefer `./scripts/bump-version.sh`: - `./scripts/bump-version.sh` (minor) - `./scripts/bump-version.sh patch|major|X.Y.Z` - Ensure both `MARKETING_VERSION` and `CURRENT_PROJECT_VERSION` are updated. 6. Commit and push branch: - Stage release files (changelog + version updates). - Commit with `Bump v