This release includes 1 breaking change for platform teams planning a safe upgrade.
Published 19d
Containers & Orchestration
✓ No known CVEs patched
✓ No known CVEs patched in this version
Topics
ai
ai-agent
ai-infra
kubernetes
sandbox
Affected surfaces
auth
breaking_upgrade
Summary
AI summaryUpdates Breaking Changes, What's New, and iptables/nft across a mixed release.
Full changelog
What's New
Breaking Changes
- The credential vault binding match no longer carries a
Portsfield. Port is now derived from the scheme (https→ 443,http→ 80), matching what the intercept layer (iptables/nft) actually redirects. If your Go code constructs credential vault bindings and setsMatch.Ports, remove that field on upgrade — port selection is now implicit from the scheme. This removes a field that never provided real flexibility (only 80/443 were ever intercepted). #1189
Features
- Added a client-side sandbox pool (OSEP-0005) for the Go SDK, enabling millisecond-level sandbox acquisition from pre-warmed idle instances. The new
SandboxPoolAPI (viaPoolBuilder) provides a background reconcile loop with leader election, fill-deficit / shrink-excess management, exponential backoff on warmup failures, and near-expiry-aware idle reuse.InMemoryPoolStateStorecovers single-process deployments; a separate optionalpoolredissub-module (go-redis v9) providesRedisPoolStateStorewith atomic Lua-script operations for distributed setups. The main SDK module stays ongo 1.20with zero external dependencies — the pool is a fully opt-in, backward-compatible addition. Aligned with the Python and Kotlin pool implementations. #1198 - Added
run_onceandwithSessionisolation convenience helpers to the Go SDK.sandbox.IsolationRunOnce(ctx, req, run, handlers)wraps create → run → delete into a single call with guaranteed cleanup, andsandbox.IsolationWithSession(ctx, req, fn)scopes a multi-run isolated workflow with auto-delete on exit. Cleanup is best-effort so it never masks the original error. These build on the execd-backed isolation support added to the Go SDK (isolated.go,sandbox_isolated.go). #1008 #1222 - Added an LRU + TTL endpoint cache with in-flight request deduplication. The SDK now caches
(sandbox_id, port, use_server_proxy) → Endpointto avoid repeated resolution round-trips. It is enabled by default (TTL 600s, max size 1024) and tunable viaConnectionConfig;Kill()actively invalidates cached entries for the sandbox. #1133 - Sandbox lifecycle responses now surface
extensions. The Go SDK response models exposeopensandbox.extensions.*data returned by create/get/list so callers can read extension values round-tripped from the server. #1112 - Added the optional
resourceRequestsfield to sandbox creation. Kubernetes-backed sandboxes can now set resource requests separately from limits (enabling Burstable QoS). Omitting the field preserves the existing behavior where requests equal limits. #1074
Misc
- Updated the Go SDK README GitHub links to the new
opensandbox-group/OpenSandboxorg (Go module/import paths unchanged). #1197 - Bumped the Go Sandbox SDK version constant to
1.0.4and added a regression test that locks the default User-Agent to the release version. #1248
Contributors
- @GreenShadeZhang
- @Pangjiping
- @jianpingpei
- @jwx0925
Breaking Changes
- Removed `Ports` field from credential vault binding match; port selection is now implicit based on scheme (`http` → 80, `https` → 443).
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Earlier breaking changes
- vpython/sandbox/v0.1.14 Removes `CredentialMatch.ports`; port now derived from scheme.
- vjava/sandbox/v1.0.16 Removes CredentialMatch.ports; port derived from scheme instead.
- vdocker/egress/v1.1.4 `Match.Ports` field removed from Credential Vault bindings; ports derived from scheme.
- vdocker/egress/v1.1.4 'X-Forwarded-Proto' is trusted only from configured proxy CIDRs.
- vdocker/egress/v1.1.4 Credential Vault requires `dns+nft` enforcement for egress connections.
Beta — feedback welcome: [email protected]