Packages

@cloudflare/containers

0.3.7 · 4 Jun 2026MIT OR Apache-2.03M / weekRepositoryHomepagenpmAtom feed

Upgrading @cloudflare/containers From 0.3.3 to 0.3.7

4 releases in betweenevery note read

Reading releases, release notes and advisories…

0
changes to make
0
advisories fixed
1
new
12
fixes

Release by release

  1. 0.3.7

    4 Jun 20261 fix
    • Fixed

      Prevent startup and stop handling races from persisting a stopped state for a running container.

  2. 0.3.6

    1 Jun 20262 fixes
    • Fixed

      Use IdentityTransformStream when proxying deferred HTTP response bodies.

    • Fixed

      Remove noisy logs emitted while checking container and port readiness.

  3. 0.3.5

    27 May 20261 new · 5 fixes
    • New

      Add return types to exported functions and public methods to satisfy ESLint and improve type checking.

    • Fixed

      Use the canonical AlarmInvocationInfo type from @cloudflare/workers-types for the alarm() parameter instead of an inline type. This is a no-op for users (the shape is identical), but keeps the override aligned with the Durable Object base class signature.

    • Fixed

      Clarify the license for this library matches that of @cloudflare/workers-sdk, which is dual licensed under either MIT OR Apache-2.0.

    • Fixed

      Tighten the return type of Container#onError from any to unknown. Subclasses that override onError can still return any value. This should be a no-op for most users.

    • Fixed

      Preserve original errors as cause when wrapping abort/timeout errors during container startup, making it easier to debug the underlying failure.

    • Fixed

      Reset container state after failed startup or terminal monitor errors, avoid stale monitor callbacks updating newer instances, and apply configured constructor startup options.

  4. 0.3.4

    11 May 20264 fixes
    • Fixed

      Fix a race in Container where concurrent container.fetch calls to a cold container could throw "start() cannot be called on a container that is already running.".

    • Fixed

      Ensure pending stop events are processed when the persisted container lifecycle state is still running but the underlying container has already exited.

    • Fixed

      Fix subclass sleepAfter overrides being ignored during the initial activity timeout setup. Previously, the base Container constructor called renewActivityTimeout() inside blockConcurrencyWhile() before subclass class-field initializers ran, so the first sleepAfterMs was always computed from the base default ('10m') regardless of whether the subclass declared sleepAfter = '2h'. A container could then be killed by the activity timeout before the subclass's longer window took effect on the next renewActivityTimeout call. Declarations like:

    • Fixed

      Preserve Cloudchamber startup rate-limit errors in the Containers helper and return HTTP 429 from containerFetch() when startup is rate limited.

3 other lines we could not sort, mostly version bumps
  • All examples now use the latest TypeScript, Vitest, and Wrangler, and target a current Workers compatibility_date.

    0.3.5
  • Worker types are generated by wrangler types, matching current Cloudflare guidance.

    0.3.5
  • The examples/timeout/ snippet is now a fully runnable example.

    0.3.5

1 internal line (docs, tests, tooling) left out.

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.