Agentic Sandbox v2026.5.2
Agentic Sandbox v2026.5.2
Released: 2026-05-19 Tag: `v2026.5.2` Previous: `v2026.5.1` (2026-05-19) Compare: `v2026.5.1...v2026.5.2`
Source-only release. No binaries, container images, or SBOMs are attached. Build from source via `make build`. Release-artifact CI is tracked under #295, #297, #299, #300, #304, #305 and will produce the first artifact-bearing release in a follow-up cut.
What this release is
A small patch release on top of v2026.5.1. Three commits, no behavior change for v1 or v2 clients. The substantive ship is a conformance-CI stability fix for transient rustc SIGSEGV under self-hosted runner contention; the rest is documentation and release-pipeline honesty.
If you are running v2026.5.1: rebuild from this tag if you care about the README clone URL, the conformance fix, or want the source-only notice on the v2026.5.1 release page reflected locally. Otherwise this is functionally identical for runtime users.
Highlights
- Conformance harness stabilized under runner contention (#309). `conformance.yml` now serializes runs per ref, caps Rust build job parallelism, and retries only compiler-crash Rust build failures once with serialized jobs. Functional test failures still fail fast.
- Release pipeline audited (`docs/architecture/release-pipeline-audit.md`). Documents what every workflow does and doesn't do on tag push, ASCII diagram of the gap, 4-phase remediation plan, and explicit acceptance bar for the next "real" release.
- v2026.5.1 release page marked source-only in CHANGELOG and announcement.
- Public-facing clone URL switched in README + getting-started from internal Gitea to GitHub.
Changes
| Commit | Description |
|---|---|
| `1c2cc33` | `ci(conformance): harden Rust build against compiler crashes` (#309) |
| `f012773` | `docs(release): mark v2026.5.1 source-only + add release-pipeline audit` |
| `d25e1fc` | `docs: switch clone URL to GitHub in README + getting-started` |
Issues filed during this cycle
| # | Title | Priority |
|---|---|---|
| #304 | `ci.yaml` triggers on `v*` tag pushes | P1 |
| #305 | Internal registry `:v<version>` container tags | P1 |
| #306 | Sync Gitea releases to GitHub mirror Releases page | P2 |
| #307 | Re-enable `docsite-deploy.yml` on `v*` tag pushes | P2 |
| #308 | Fold `executor-build.yml` into `ci.yaml` | P3 |
These join the existing release-prep issues (#295, #296, #297, #299, #300, #301). Phases 1–3 of the audit (`docs/architecture/release-pipeline-audit.md` § 6) must land before the next release can claim to ship artifacts.
Upgrade notes
| If you are… | Do this |
|---|---|
| Running v2026.5.1 with no contributions to the codebase | Optional rebuild from `v2026.5.2`. No runtime behavior change. |
| Maintaining or contributing to the project | `git pull && cd management && cargo build --release` (and `agent-rs`, `cli`). Pick up the conformance CI fix so your PRs don't get flagged by intermittent rustc crashes. |
| Operating a sandbox in production | No upgrade required. Wait for the next release that actually ships artifacts (post Phase 2 of the pipeline audit). |
How to verify the upgrade
git fetch --tags origin
git checkout v2026.5.2
make build
# Verify versions
./management/target/release/agentic-mgmt --version # 2026.5.2
./cli/target/release/sandboxctl --version # 2026.5.2
./agent-rs/target/release/agent-client --version # 2026.5.2Full change log
See `CHANGELOG.md` for the detailed entry.