Release

Release

Create a versioned GitHub release with an auto-generated changelog from commits since the last release.

Step 1: Determine Version

Check the current version and latest git tag:

cat package.json | grep '"version"'
git tag -l --sort=-v:refname | head -5

If the user provided a version, use it. Otherwise ask:

What version? (current is X.Y.Z — patch/minor/major, or exact version)

Resolve semver:

• patch → X.Y.(Z+1)
• minor → X.(Y+1).0
• major → (X+1).0.0
• Exact version string → use as-is

Step 2: Generate Changelog

Get commits since the last tag (or all commits if no tags exist):

# If tags exist:
git log $(git tag -l --sort=-v:refname | head -1)..HEAD --pretty=format:"- %s" --no-merges

# If no tags:
git log --pretty=format:"- %s" --no-merges

Group commits by type using conventional commit prefixes:

Format as markdown. Omit empty sections. Strip the type(scope): prefix from each line for readability.

Always start the changelog with this install block (hardcoded):

Install:

```bash
pi install git:github.com/HazAT/pi-solo@v<VERSION>
```

Or latest:

```bash
pi install git:github.com/HazAT/pi-solo
```

Then add the grouped commit sections below it.

Example output:

## ✨ Features

- Idle-close the helper subprocess so it stops appearing under Pi's row in Solo
- Render Solo keyboard shortcut hints on spawn/start/restart/status results

## 🐛 Bug Fixes

- Don't crash when MCP is disabled in Solo settings — poll for re-enable
- Handle tools with empty inputSchema

Step 3: Run Tests

Before tagging, confirm the unit tests pass:

npm test

Stop and surface failures if anything is red.

Step 4: Update package.json

Bump the version in package.json:

# Read, update, write back — don't use npm version (it may auto-commit)

Use a precise edit to change only the version field.

Step 5: Commit, Tag, Push

git add package.json
git commit -m "chore(release): v<VERSION>"
git tag v<VERSION>
git push && git push --tags

Step 6: Create GitHub Release

gh release create v<VERSION> --title "v<VERSION>" --notes "<CHANGELOG>"

Pass the generated changelog as the --notes value. Use a temp file if the changelog is long:

echo "<CHANGELOG>" > /tmp/release-notes.md
gh release create v<VERSION> --title "v<VERSION>" --notes-file /tmp/release-notes.md
rm /tmp/release-notes.md

Step 7: Verify

Confirm the release was created:

gh release view v<VERSION>

Print a summary:

✅ Released v<VERSION>
   Tag: v<VERSION>
   URL: https://github.com/HazAT/pi-solo/releases/tag/v<VERSION>

Source: HazAT/pi-solo — distributed by TomeVault.