e2b@2.52.1
E2B 2.52.1 aligns .dockerignore context filtering with BuildKit, refines retry logic to avoid duplicate creations on 502 errors, bumps dependencies, and fixes JS SDK watch handle shutdown behavior.
Why this signal matters
E2B patch release 2.52.1 introduces several bug fixes and reliability improvements: - Context filtering via .dockerignore now aligns with BuildKit: wildcard prefixes matching literal chars work at any depth, negated parent directory patterns properly avoid re-inclusion, and JS SDK regex handling handles non-BMP characters like emoji as single characters. - Retry logic adjustments: 502 Bad Gateway responses are no longer retried on non-idempotent resource-creation endpoints (sandbox creation, fork, snapshot) or secret updates (POST /secrets/{id}) to prevent accidental duplicates or unintended version increments. 503 responses remain globally retried. - JS SDK fix: Invoking WatchHandle.stop() now correctly signals a clean exit via onExit without throwing a false TimeoutError. - Dependency updates: Bumps undici (^7.30.0), undici8 (8.11.2), compare-versions (^6.1.1), and inquirer (^12.11.1).
Actionable summary
E2B version 2.52.1 updates .dockerignore parsing to match BuildKit behavior (including multi-byte char handling in JS), disables automatic retries on 502 responses for non-idempotent operations (sandbox creation, fork, snapshot, secret updates), bumps undici and CLI dependencies, and resolves an issue where WatchHandle.stop() in the JS SDK triggered a false TimeoutError.
- Agent usefulness
- 77/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Upgrade e2b and @e2b/cli to version 2.52.1.
- Review custom retry logic around sandbox creation, forks, snapshots, and secret updates to account for 502 errors now being propagated instead of automatically retried by the SDK.