# Release

> Automate the full hoverfly release process — version bump, GitHub release, wait for CI, trigger Homebrew update.

- Skill: `spectolabs/release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add spectolabs/release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/spectolabs/release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: spectolabs (https://skillmd.com/u/spectolabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/spectolabs/release

---


# Hoverfly Release

Release version: **$ARGUMENTS**

## Current state

- Current version: !`grep 'hoverfly.version' core/hoverfly.go | grep -o 'v[0-9]*\.[0-9]*\.[0-9]*'`
- Branch: !`git branch --show-current`
- Working tree clean: !`git status --porcelain | wc -l | xargs`

## Instructions

Execute the following phases in order. Confirm with the user before moving to each phase. Stop immediately if any step fails.

### Phase 1 — Version bump & push

1. **Validate** that `$ARGUMENTS` matches the pattern `vX.Y.Z` (e.g. `v1.13.0`). If not, stop and ask the user for a valid version.
2. **Verify** the working tree is clean (`git status --porcelain` is empty) and the current branch is `master`. If not, stop and tell the user.
3. Run: `make update-version VERSION=$ARGUMENTS`
4. Push: `git push origin master`

Tell the user the version commit has been pushed and that a CircleCI build has been triggered (no need to wait for it).

### Phase 2 — Create GitHub release

1. Create the release with auto-generated notes:
   ```
   gh release create $ARGUMENTS --generate-notes --target master
   ```
2. Show the user the release URL.
3. Tell the user this has triggered the CircleCI `deploy-release` job, which will build cross-platform binaries and Docker images. This typically takes 20+ minutes.

### Phase 3 — Wait for release assets

Poll once per minute until **all 7** expected zip bundles appear in the release assets. The expected files are:

- `hoverfly_bundle_OSX_amd64.zip`
- `hoverfly_bundle_OSX_arm64.zip`
- `hoverfly_bundle_windows_amd64.zip`
- `hoverfly_bundle_windows_386.zip`
- `hoverfly_bundle_linux_amd64.zip`
- `hoverfly_bundle_linux_386.zip`
- `hoverfly_bundle_linux_arm64.zip`

To check, run this (counts how many of the 7 expected bundles are present).
It is shell-agnostic — works in sh, bash, and zsh:
```
gh release view $ARGUMENTS --json assets --jq '.assets[].name' > /tmp/hf_release_assets.txt
printf '%s\n' \
  hoverfly_bundle_OSX_amd64.zip \
  hoverfly_bundle_OSX_arm64.zip \
  hoverfly_bundle_windows_amd64.zip \
  hoverfly_bundle_windows_386.zip \
  hoverfly_bundle_linux_amd64.zip \
  hoverfly_bundle_linux_386.zip \
  hoverfly_bundle_linux_arm64.zip \
  | grep -Fxf - /tmp/hf_release_assets.txt | wc -l | xargs
```

> NOTE: Keep the count shell-agnostic. The command above relies only on POSIX
> features (`printf`, a pipe, `grep -Fxf -` reading patterns from stdin, a temp
> file) — no process substitution `<(...)`, no arrays, no unquoted word-splitting.
> Do NOT count with `for e in $expected; do grep -qx "$e"; done`: in zsh,
> unquoted `$expected` is NOT word-split, so the loop runs once over the whole
> string and always reports `0/7`.

Each poll iteration:
- Run the command above to get the count (0–7)
- Report progress to the user: "X/7 assets uploaded..."
- Sleep 60 seconds between checks
- After 45 minutes with no completion, warn the user and ask whether to keep waiting

### Phase 4 — Trigger Homebrew update

Once all 7 assets are confirmed:

1. Trigger the Homebrew formula bump workflow:
   ```
   gh workflow run homebrew-bump-formula.yml -f version=$ARGUMENTS
   ```
2. Tell the user the workflow has been triggered and they need to manually merge the resulting PR in `SpectoLabs/homebrew-tap`.

### Done

Summarize what was completed:
- Version bumped to `$ARGUMENTS`
- GitHub release created with auto-generated notes
- All 7 platform bundles uploaded by CircleCI
- Homebrew formula update triggered
- Remaining manual step: merge the PR in `SpectoLabs/homebrew-tap`