Packages

@cloudflare/sandbox

1.0.3 · 22 Oct 2026Apache-2.02.1M / weekRepositoryHomepagenpmAtom feed

Upgrading @cloudflare/sandbox From 0.12.4 to 0.12.5

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 0.12.4Newest 0.x0.12.14Latest1.0.3
  1. 0.12.4yours
  2. 0.12.5target
0
changes to make
0
advisories fixed
0
new
0
fixes
7 other lines we could not sort, mostly version bumps
  • Instrument the bridge API with Cloudflare custom spans. Each endpoint now emits a bridge.<operation> span annotated with the sandbox ID, container UUID, and operation-specific metadata (command, file path, port, session ID, and so on), so requests are traceable end to end. Enable tracing with observability.traces.enabled in your Worker configuration.

    0.12.5
  • Make destroy() succeed when the sandbox container was never admitted, so cleanup no longer fails with a no-instance platform error.

    0.12.5
  • Reduce intermittent startup failures during concurrent sandbox creation where operations could fail with a disposed RPC session error.

    0.12.5
  • Surface container capacity and admission failures as retryable ContainerUnavailableError with a structured reason, including no-instance and max-instances cases. Callers can branch on error.reason instead of parsing platform messages.

    0.12.5
  • Fill the warm pool in bounded-parallel batches instead of one container at a time, so it primes and recovers far faster after a burst. Tune the batch size with WARM_POOL_SCALE_BATCH_SIZE (default 5, clamped to 20).

    0.12.5
  • Refill the warm pool the moment it drains instead of waiting for the next background tick. After a burst consumes warm containers, replenishment now starts immediately, cutting the latency tail for sandboxes created during sustained or back-to-back bursts.

    0.12.5
  • Let the warm pool know its instance ceiling up front via the WARM_POOL_MAX_INSTANCES bridge variable. Set it to match your container's max_instances so the pool makes correct capacity decisions without first crashing into the limit. 0 (the default) preserves the existing auto-learn behaviour.

    0.12.5

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.