Skip to content

v0.1.34

Choose a tag to compare

@github-actions github-actions released this 16 Nov 23:09
· 49 commits to main since this release
ef9068b

⚠️ Isolation suites were not run for this tag

The Cilium packet-level suite and the Kata boot probe did not execute, so
tenant isolation is unverified and the control and guest image digests
were not verified by them. This release continues only because a
workflow_dispatch run set isolation_skip=true (acknowledgement none):
a tag push cannot take this path.

Set SANDBOX_ISOLATION_RUNNER and re-run the release without the skip
input. See docs/release-process.md#isolation-gate.

What's Changed

Full Changelog: v0.1.33...v0.1.34

Images

Multi-arch (linux/amd64, linux/arm64), published to GHCR:

  • ghcr.io/ejackson-vp/sandbox-control:v0.1.34
  • ghcr.io/ejackson-vp/sandbox-guest:v0.1.34

These tags were created only after both images passed the Trivy
gate. Each image carries an SBOM and SLSA build provenance as OCI
attestations:

docker buildx imagetools inspect ghcr.io/ejackson-vp/sandbox-control:v0.1.34

Verifying provenance

The *.sigstore.json assets are keyless Sigstore bundles produced by
this workflow, covering exactly the digests above. Verify the image
itself:

gh attestation verify \
  oci://ghcr.io/ejackson-vp/sandbox-control:v0.1.34 \
  --repo ejackson-vp/sandbox

Add --bundle-from-oci to check the attestation stored in the
registry instead of the one on GitHub.

*.intoto.jsonl is the in-toto statement carried inside the bundle,
for SLSA tooling that consumes statements rather than bundles.

The guest image is what runs inside the microVM and must match the
cluster architecture. CVE results for this tag are in the Security
tab (trivy-control, trivy-guest).

Staging images from the build (staging-<run-id>-<sha>) are not
release artifacts; see docs/release-process.md for cleanup.