Development

Build

go build -o bin/holos ./cmd/holos
go test ./...
go test -race ./...
go run golang.org/x/vuln/cmd/govulncheck@v1.6.0 ./...
go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.12

Build a guest image with mkosi:

./scripts/build-image.sh

Host Requirements

Runtime commands need a Linux KVM host with:

macOS builds are shipped for offline work: validate, import, images, pull, and compose-file authoring.

Cutting A Release

Before tagging:

  1. Update main and confirm CI and the KVM smoke workflow pass.
  2. Add the release notes to CHANGELOG.md.
  3. Update the install version in README.md and docs/index.md.
  4. Commit and push those documentation changes.

Choose the next version, then publish the tag. This triggers the release workflow and publishes the binaries automatically:

git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin vX.Y.Z

The workflow cross-compiles Linux and macOS binaries for amd64 and arm64, packages them with LICENSE, NOTICE, and README.md, computes SHA-256 checksums, publishes a GitHub release, and emits GitHub artifact attestations. Release notes keep the checksum file and signed provenance verification command visible near the install command so operators can verify downloads before extracting them.

After the workflow finishes, confirm the release contains all four platform archives and checksums.txt, and that the provenance attestation step passed.

To rehearse locally without publishing:

goreleaser release --snapshot --clean --skip=publish