Agent InfrastructureAutomated release watch

e2b@2.50.0

E2B 2.50.0 cleans up legacy V1 template endpoints from client libraries, fixes browser-specific upload and error-reporting bugs, resolves Azure storage build upload issues, and updates dependencies.

Human read

Why this signal matters

E2B version 2.50.0 introduces several minor and patch changes across its generated API clients and runtime integrations. The release removes deprecated V1 template build operations (POST /templates, POST /templates/{templateID}, POST /templates/{templateID}/builds/{buildID}, POST /v2/templates) and related schemas from the generated JavaScript and Python API clients, as control planes return 410 Gone for these endpoints in favor of the Template SDK. The client updates also document 429 status codes on most operations, 409 on template create (v3), upload-request headers on file-upload links, minLength: 1 on v2 build source fields, and a deprecation marker on the logs field of build status. Bug fixes include applying required upload headers (x-ms-blob-type) returned by the API to fix COPY instructions on Azure-backed clusters, draining non-native browser ReadableStreams via readers rather than new Response(stream) to avoid stringification, properly recognizing browser network drop messages to surface killed sandboxes as TimeoutError instead of generic SandboxError, and updating @connectrpc packages (2.2.0) and undici (7.29.1 / undici8 8.10.2).

Agent parse

Actionable summary

E2B 2.50.0 removes deprecated V1 template build schemas/operations (returning 410 Gone; Template SDK required instead), handles upload request headers for Azure Blob Storage, resolves browser-specific ReadableStream upload and TimeoutError reporting bugs, and bumps connectrpc and undici.

Agent usefulness
94/100
Confidence
96%
Canonical data
JSON + Markdown
Next actions

What builders should check

  • Remove direct imports of legacy V1 template models and endpoints (e.g., TemplateLegacy, TemplateBuildRequest, TemplateBuildRequestV2) from generated Python and JS client packages.
  • Ensure any custom template build workflows migrate from deprecated V1 endpoints to the official Template SDK.
  • Verify file uploads using ReadableStream in browser environments if previously relying on non-native stream classes.
Classification

Tags and routing

sandboxcode-executionagents
Related signals

Continue the thread