Releasing

Releases are published by the release workflow when a version tag is pushed:

git tag v1.1.0
git push origin v1.1.0

It then:

1. Builds the UI and cross-compiles the binary for Linux, macOS and Windows on amd64 and arm64, with the version from the tag embedded (testhooks --version).
2. Attaches the binaries and a checksums.txt to the GitHub release, creating the release with generated notes if it doesn’t exist.
3. Builds and pushes a multi-arch image to ghcr.io/sarathsp06/testhooks:<version> and :latest.

The installer script and the standalone Compose file download from these.

To republish an existing tag, run the workflow manually from the Actions tab and enter the tag.

First release

GitHub Container Registry makes a newly published package private. After the first release, open the package’s settings on GitHub and set its visibility to public, or the Compose file won’t be able to pull the image.

Documentation

This site is built with Starlight from the docs/ directory and deployed to GitHub Pages by the docs workflow on every push to main that touches docs/.

cd docs
npm ci
npm run dev       # http://localhost:4321/testhooks/