Agentic Sandbox v2026.6.33
Agentic Sandbox v2026.6.33
Released: 2026-06-26 Tag: `v2026.6.33` Previous: `v2026.6.32` Compare: `v2026.6.32...v2026.6.33`
What this release is
v2026.6.33 is the follow-up release-flow cut for the QEMU/vsock transport line. It keeps the v2026.6.32 runtime surface and focuses on the operational failure that appeared after the release gate: stale runner-local base images and brittle release automation could block reproducible E2E and publication.
The operator-facing result is that the base-image builder is now safe to run from automation, stale image replacement requires explicit intent, and the tag publication workflow keeps the release mirror sidecars on a YAML-valid path.
Highlights
- Automation-safe base-image rebuilds (#585): `images/qemu/build-base-image.sh`
now accepts `--yes`/`--force` for intentional replacement and refuses non-interactive overwrite of an existing qcow2 unless that intent is explicit.
- Early runner-state diagnostics (#585): the builder fails before guest
provisioning when `/mnt/ops/base-images` is not writable, avoiding long image bakes that cannot install their result.
- Source-safe script tests (#585): the image builder can be sourced by
shell regression tests without implicitly entering `main`.
- Release publication lane kept valid: release mirror sidecar container
declarations now use YAML-valid list syntax for the tag workflow path.
Operator notes
- If E2E reports image/manifest drift for
`ubuntu-server-24.04-agent.qcow2`, repair the affected runner by either rebuilding with `images/qemu/build-base-image.sh 24.04 --yes` or installing a verified image and manifest pair from titan.
- The grissom runner was repaired with the verified titan image hash
`a8d2b97b14eb45215f1f333ec2f4ed7dae751c217b07e3c59aae9fac374008c1`; the replacement image was marked immutable after install.
- Existing v2026.6.32 runtime guidance still applies for the QEMU/vsock line.
Quality
- Local release-flow checks for the base-image automation fix passed:
`bash -n`, shellcheck, the new image-build shell regression suite, and `make test-scripts`.
- Gitea Actions run `1793` passed on `e0de9f8a1c99017c347df0af698a5dbb11c55348`,
including Docker publish, security scan, and release-blocking E2E.
- E2E job `58016` passed all six runtime tests and reaped its scoped VM.