E2 B

From the release notes

Patch Changes 5b015ad: Removed the hidden e2b template build command (alias bd). It printed a V1 deprecation notice and exited 1; the V1 build system it fronted is gone from the API. A script still calling it now gets commander's unknown-command error with the same exit code. Build templates with e2b template create or the Template SDK; e2b template migrate still converts a V1 project (see https://e2b.dev/docs/template/migration-v2). Updated dependencies [956e3ab] Updated dependencies [e1fbe86] Updated dependencies [80496c0] Updated dependencies [5b015ad] Updated dependencies [80496c0] Updated dependencies [e1fbe86] e2b@2.50.0

From the release notes

Minor Changes 5b015ad: Removed the V1 template build operations and schemas from the generated API clients. The API no longer serves them (runtime 87968fc1e1fa); control planes carrying that change answer 410 Gone. Template builds go through the Template SDK. Visible removal, classified minor: the JS paths namespace loses POST /templates, POST /templates/{templateID}, POST /templates/{templateID}/builds/{buildID} and POST /v2/templates, and components['schemas'] loses TemplateLegacy, TemplateBuildRequest and TemplateBuildRequestV2; the Python e2b.api.client.models package loses TemplateLegacy, TemplateBuildRequest and TemplateBuildRequestV2, and e2b.api.client.api.templates loses the post_templates, post_templates_template_id, post_templates_template_id_builds_build_id and post_v2_templates modules. No SDK method accepted or returned them; code that imported these names directly must drop the import. The regenerated clients also pick up a documented 429 on most operations, a 409 on template create (v3), the upload-request headers on the build file-upload link, minLength: 1 on the v2 build source fields, and a deprecation marker on the always-empty logs field of the build status. Patch Changes 956e3ab: Apply the request headers the API returns with a template layer-file upload link. Azure Blob Storage requires x-ms-blob-type on the upload request, which its signed URL cannot carry, so COPY instructions failed on Azure-backed clusters. GCS- and S3-backed clusters return no headers and are unaffected. e1fbe86: Bump @connectrpc/connect and @connectrpc/connect-web to 2.2.0 (fixes Http2SessionManager.verify() hanging when the connection closes mid-verification and stops delivering stream messages after cancellation). 80496c0: Fix uploads of non-native ReadableStreams in the browser silently sending the text [object ReadableStream] instead of the data. Buffering a stream drained it with new Response(stream), which accepts any async iterable on Node (an undici extension) but only its own stream class in a browser, stringifying anything else. Streams are now drained through the reader, which every implementation supports. 80496c0: Report a sandbox killed mid-request as an actionable TimeoutError in the browser. When the connection to a sandbox drops mid-request the SDK probes the sandbox's health to tell a killed sandbox apart from a transient network blip, but the probe only ran for connection-dropped wordings it recognized, and the browser's (network error) was missing — so killing a sandbox while a command was running surfaced a generic SandboxError: [unknown] network error instead of TimeoutError: ... The sandbox was killed or reached its end of life while the request was in flight. e1fbe86: Bump undici to 7.29.1 and the optional undici8 fallback to 8.10.2 to pick up the September 2026 security fixes.

From the release notes

Minor Changes 5b015ad: Removed the V1 template build operations and schemas from the generated API clients. The API no longer serves them (runtime 87968fc1e1fa); control planes carrying that change answer 410 Gone. Template builds go through the Template SDK. Visible removal, classified minor: the JS paths namespace loses POST /templates, POST /templates/{templateID}, POST /templates/{templateID}/builds/{buildID} and POST /v2/templates, and components['schemas'] loses TemplateLegacy, TemplateBuildRequest and TemplateBuildRequestV2; the Python e2b.api.client.models package loses TemplateLegacy, TemplateBuildRequest and TemplateBuildRequestV2, and e2b.api.client.api.templates loses the post_templates, post_templates_template_id, post_templates_template_id_builds_build_id and post_v2_templates modules. No SDK method accepted or returned them; code that imported these names directly must drop the import. The regenerated clients also pick up a documented 429 on most operations, a 409 on template create (v3), the upload-request headers on the build file-upload link, minLength: 1 on the v2 build source fields, and a deprecation marker on the always-empty logs field of the build status. Patch Changes 956e3ab: Apply the request headers the API returns with a template layer-file upload link. Azure Blob Storage requires x-ms-blob-type on the upload request, which its signed URL cannot carry, so COPY instructions failed on Azure-backed clusters. GCS- and S3-backed clusters return no headers and are unaffected.

From the release notes

Patch Changes 5e418dc: Document that onResume / on_resume needs a control plane that knows the option: an older self-hosted or BYOC control plane drops the memory field and restores memory while reporting success, instead of rejecting the request. 9136603: Retry control-plane HTTP requests up to three times after 429 responses using the server's delta-seconds Retry-After delay. Retries can be configured or disabled with retries, and stop when waiting would exhaust the request timeout. Envd requests, including filesystem operations, and volume-content requests are not retried.

From the release notes

Patch Changes 90e3fc5: Reject invalid Sandbox.create lifecycle options and Sandbox.connect onResume values before requiring an API key, matching the Python SDK. 5e418dc: Document that onResume / on_resume needs a control plane that knows the option: an older self-hosted or BYOC control plane drops the memory field and restores memory while reporting success, instead of rejecting the request. 9136603: Retry control-plane HTTP requests up to three times after 429 responses using the server's delta-seconds Retry-After delay. Retries can be configured or disabled with retries, and stop when waiting would exhaust the request timeout. Envd requests, including filesystem operations, and volume-content requests are not retried.