-
Notifications
You must be signed in to change notification settings - Fork 0
Go Release Packaging
Huzefaaa2 edited this page May 18, 2026
·
65 revisions
CAVRA now includes a release packaging workflow for the Go enforcement-plane runtime.
.github/workflows/go-release.yml- Linux, macOS, and Windows builds for
amd64andarm64. -
checksums.txt. - SPDX-style SBOM:
cavra-runtime.sbom.spdx.json. - SLSA provenance:
cavra-runtime.provenance.intoto.json. - Release evidence:
release-evidence.jsonandrelease-evidence.md. - Detached Ed25519 signature JSON files when
CAVRA_GO_RELEASE_SIGNING_KEYis 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.
gh workflow run go-release.yml --repo Huzefaaa2/cavra \
-f version=dry-run \
-f dry_run=trueFor 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.0Verify an unsigned dry-run package:
cavra release verify-go-package go/cavra-runtime/dist/go-runtime-dry-run --allow-unsigned- As a release manager, I can publish Go binaries with release evidence and provenance.
- As a security engineer, I can validate checksums, SBOM metadata, SLSA provenance, and detached signatures.
- As an enterprise architect, I can review binary distribution controls before air-gapped rollout.
- As an auditor, I can run a local verifier before approving runtime distribution.
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, and CLI verification reduce manual release-review steps.
Connect the public sandbox to backend-driven scenario runs and add keyless release attestations with GitHub OIDC.
CAVRA Field Compass
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
| Start | Build | Operate | Assure |
|---|---|---|---|
| Quick Start | CLI | Enterprise Guide | AISPM |
| Reader Paths | Policy Syntax | Deployments | Evidence |
| Community | GUI | Troubleshooting | Conclusion |
Textbook home: Before the Agent Acts |
Development archive: development and testing artifacts |
Source repository: github.com/Huzefaaa2/cavra
- Foreword And Reader Paths
- Why CAVRA Exists
- Runtime Authority Model
- Architecture
- Editions
- Install And Deploy
- Community Guide
- Enterprise Guide
- CLI Reference
- GUI And Sandbox
- AISPM Guide
- Policy And Evidence
- Operations And Integrations
- Labs And Use Cases
- Appendices And FAQ
- Policy Language Reference
- Troubleshooting Playbook
- Conclusion