complete-release - SKILL.md Agent Skill

name: complete-release description: > Finalize a mainline solana-keychain release after the PR is approved: approve, squash-merge, and trigger both publish workflows from main via gh CLI. Use when asked to "finalize release", "merge release PR", "complete release", "publish packages", or "approve and merge release".

Complete Release Skill

This is the reviewer half of the mainline release flow. Run this after a release PR to main has been reviewed and is ready to merge.

Notes:

This skill is mainline-only: it dispatches publish workflows from main.
Hotfix releases are published from hotfix/* before merge-back and are handled in .claude/skills/release/SKILL.md.
Publish workflows allow both main and hotfix/* refs.

Prerequisites

gh CLI installed and authenticated (gh auth status)
You are a repo collaborator with write access

Step 1: Identify the release PR

If a PR number is not provided, find it:

gh pr list --base main --state open | grep chore/release

Note the PR number (e.g. 42).

Step 2: Approve the PR

gh pr review <PR_NUMBER> --approve --body "LGTM"

Step 3: Confirm CI is green, then squash merge

Check that all required status checks have passed before merging:

gh pr checks <PR_NUMBER>

All checks should show pass. Once green:

gh pr merge <PR_NUMBER> --squash --delete-branch

Wait for merge to complete before proceeding.

Step 4: Detect what changed and trigger publish workflows from main

Check which paths the merged PR touched, then trigger only the relevant workflow(s):

# Get the files changed by the merged PR
FILES=$(gh pr view <PR_NUMBER> --json files --jq '.files[].path')

CHANGED_RUST=$(echo "$FILES" | grep -q "^rust/" && echo "yes" || echo "no")
CHANGED_TS=$(echo "$FILES" | grep -q "^typescript/" && echo "yes" || echo "no")

echo "Rust changed: $CHANGED_RUST"
echo "TypeScript changed: $CHANGED_TS"

If Rust changed (rust/Cargo.toml, rust/CHANGELOG.md, etc.):

gh workflow run "Publish Rust Crate" \
  --repo solana-foundation/solana-keychain \
  --ref main \
  -f publish-to-crates=true \
  -f create-github-release=true

If TypeScript changed (typescript/packages/*/package.json, etc.):

gh workflow run "Publish TypeScript Packages (Manual)" \
  --repo solana-foundation/solana-keychain \
  --ref main \
  -f package=all \
  -f publish-to-npm=true \
  -f create-github-release=true

Step 5: Verify workflows started

Only check workflows that were triggered:

gh run list --workflow="Publish Rust Crate" --limit 1
gh run list --workflow="Publish TypeScript Packages (Manual)" --limit 1

Each triggered workflow should show queued or in_progress.

Verification

Once workflows complete:

If Rust was published: confirm vX.Y.Z tag exists on GitHub and crates.io shows the new version
If TypeScript was published: confirm ts-keychain-vA.B.C tag exists on GitHub and @solana/keychain on npm shows the new version