Go Release Packaging

Go Release Packaging

CAVRA now includes a release packaging workflow for the Go enforcement-plane runtime.

Delivered

• .github/workflows/go-release.yml
• Linux, macOS, and Windows builds for amd64 and arm64.
• checksums.txt.
• SPDX-style SBOM: cavra-runtime.sbom.spdx.json.
• SLSA provenance: cavra-runtime.provenance.intoto.json.
• Release evidence: release-evidence.json and release-evidence.md.
• Detached Ed25519 signature JSON files when CAVRA_GO_RELEASE_SIGNING_KEY is configured.
• Required signing for real release events and non-dry-run manual packaging.
• Dry-run mode for validation before production releases.
• GitHub Release asset attachment for signed production packages.
• CLI verification with cavra release verify-go-package.

How To Use

gh workflow run go-release.yml --repo Huzefaaa2/cavra \
  -f version=dry-run \
  -f dry_run=true

For production releases, configure CAVRA_GO_RELEASE_SIGNING_KEY with an Ed25519 private key PEM and publish a GitHub release. The workflow attaches cavra-go-runtime-<version>.zip to the release.

Verify a signed package:

cavra release verify-go-package go/cavra-runtime/dist/go-runtime-v0.1.0

Verify an unsigned dry-run package:

cavra release verify-go-package go/cavra-runtime/dist/go-runtime-dry-run --allow-unsigned

User Stories

• As a release manager, I can publish Go binaries with release evidence, provenance, and GitHub keyless attestations.
• As a security engineer, I can validate checksums, SBOM metadata, SLSA provenance, detached signatures, and gh attestation verify results.
• As an enterprise architect, I can verify an air-gapped runtime zip before restricted-network transfer.
• As an auditor, I can run a local verifier before approving runtime distribution.

Enterprise Challenge Solved

Signed Go release packaging gives regulated teams an auditable path from source commit to binary artifact before CAVRA is distributed to local developer machines, CI runners, or restricted environments. Release attachment, SLSA provenance, GitHub OIDC-backed keyless attestations, offline trust bootstrap metadata, air-gapped zip verification, release-candidate upgrade validation, and CLI verification reduce manual release-review steps.

Next

Add signed installer metadata for packaged deployment targets.