release

Engineering Community

Skill notes

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

Phase 1 — Version bump & push

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. Verify the working tree is clean (git status --porcelain is empty) and the current branch is master. If not, stop and tell the user. Run: make update-version VERSION=$ARGUMENTS 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

Create the release with auto-generated notes: Show the user the release URL. 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

Phase 4 — Trigger Homebrew update

Once all 7 assets are confirmed: Trigger the Homebrew formula bump workflow: Tell the user the workflow has been triggered and they need to manually merge the resulting PR in SpectoLabs/homebrew-tap.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@SpectoLabs · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1 — Version bump & push

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. Verify the working tree is clean (`git status --porcelain` is empty) and the current branch is `master`. If not, stop and tell the user. Run: `make update-version VERSION=$ARGUMENTS` 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).

02
Phase 2 — Create GitHub release

Create the release with auto-generated notes: Show the user the release URL. 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.

03
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`

04
Phase 4 — Trigger Homebrew update

Once all 7 assets are confirmed: Trigger the Homebrew formula bump workflow: Tell the user the workflow has been triggered and they need to manually merge the resulting PR in `SpectoLabs/homebrew-tap`.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.