release-process

Guides cutting, building, and publishing signed git-manager releases via cut-release.sh.

3|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Tlahey/git-manager --skill release-process-tlahey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/Tlahey/git-manager/tree/main/.claude/skills/release-process
Command: npx skills add https://github.com/Tlahey/git-manager --skill release-process-tlahey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing git-manager involves a fragile multi-step pipeline — version bumps, changelog generation, tag pushes, signed builds, and a draft release that feeds an in-app auto-updater — with no CI test gate to catch mistakes. This Skill walks you through each checkpoint so a broken build never reaches real users. ## Core Features & Use Cases - Version bump guidance: Decide patch/minor/major by inspecting merged PRs since the last tag via the GitHub API. - Release execution: Run pnpm release (cut-release.sh) with pre-flight checks (typecheck, lint, tests, cargo fmt/clippy), choosing between CI builds and faster --local-build signing. - Draft review and publish: Verify changelog, assets, and latest.json before publishing the draft that triggers the auto-updater. - Use Case: You want to ship v1.2.0 — the Skill confirms the bump type, runs the release script, watches the build, and walks you through reviewing and publishing the draft safely. ## Quick Start Ask the assistant to prepare and publish a new git-manager release, for example by saying "let's ship v1.2.0 as a minor release with a local build".

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I release a new version of git-manager?▼

Run pnpm release with --bump=patch|minor|major or an explicit --tag=vX.Y.Z. The cut-release.sh script runs pre-flight checks, bumps versions, generates the changelog from merged PRs, pushes a tag, and produces a draft GitHub Release for review.

How do I decide between patch, minor, and major version bumps?▼

Use the GitHub generate-notes API to list PRs merged since the last tag. Choose patch for fixes and internal changes, minor for new user-visible features, and major for breaking changes such as unmigratable settings format changes.

Why can't the prepare-release GitHub Actions workflow push the release?▼

The repo's protect-main ruleset rejects pushes from the default GITHUB_TOKEN, and personal accounts cannot grant the GitHub Actions app a ruleset bypass. Releases must be pushed from an admin's machine using cut-release.sh instead.

What is the difference between --local-build and the CI release build?▼

Without --local-build, the tag push triggers release.yml on GitHub, taking 15-20+ minutes on a paid macOS runner. With --local-build, your machine builds, signs, and drafts the release in a few minutes, requiring TAURI_SIGNING_PRIVATE_KEY to be configured.

What should I check before publishing a draft GitHub release?▼

Verify the changelog body is correct, confirm the universal .dmg, .app.tar.gz, .sig, and latest.json assets are attached, and fix issues by deleting the draft and rebuilding. Publishing makes the release visible to the auto-updater immediately.

What happens if the release script fails after pushing the tag?▼

The version-bump commit and tag are already on main and the CI build likely started. Either let CI finish or fix the issue and re-run cut-release.sh --local-build, which attaches to the existing tag without re-bumping the version.