This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryUpdates 👥 Contributors, ✨ Features, and 🐛 Bug Fixes across a mixed release.
Full changelog
What's New
✨ Features
-
Custom sandbox creation for client-side pools —
SandboxPoolcan now use a custom sandbox creator when the default image/template based creation path is not enough. The default pool creation flow remains unchanged when no creator is configured, while custom-created sandboxes are still handed back to the pool for health checking, renewal, idle storage, and cleanup. This enables advanced SDK integrations without reimplementing pool coordination in user code. (https://github.com/opensandbox-group/OpenSandbox/pull/1125) -
Isolated execution session APIs — The Python SDK now exposes generated isolated-session and isolated-filesystem clients backed by the new execd isolation runtime. This adds client access to create/delete isolated sessions and perform scoped filesystem operations in the isolated execution path. The server-side diff/commit path is still deferred, so callers should treat commit support as not yet available. (https://github.com/opensandbox-group/OpenSandbox/pull/1008)
🐛 Bug Fixes
-
Preserve server error details in exception strings —
SandboxException.__str__()now includes parsedSandboxErrorcode/message andrequest_idwhen present, instead of collapsing failures to generic messages likeAPI error: HTTP 500. This makes Python client logs and surfaced exceptions actionable without requiring callers to inspect the raw error object separately. (https://github.com/opensandbox-group/OpenSandbox/pull/1122) -
Correct PVC cleanup semantics in SDK models and docs — The Python SDK model documentation for
deleteOnSandboxTerminationnow matches Kubernetes behavior: opted-in auto-created PVCs can be cleaned up when the sandbox is deleted, while the default remainsfalseand pre-existing or opt-out PVCs are left untouched. This is a documentation/model clarification for client users; existing sandboxes keep the old behavior unless they explicitly opt in. (https://github.com/opensandbox-group/OpenSandbox/pull/880)
📦 Misc
- Bumped the Python sandbox SDK fallback/version metadata to
0.1.13. (https://github.com/opensandbox-group/OpenSandbox/pull/1125)
👥 Contributors
- @Pangjiping
- @ninan-nn
- @xfgong
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]