@cloudflare/containers
0.3.7 · 4 Jun 2026MIT OR Apache-2.03M / weekRepositoryHomepagenpmAtom feed
Upgrading @cloudflare/containers From 0.0.30 to 0.3.7
16 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- Fixed
Prevent startup and stop handling races from persisting a stopped state for a running container.
- Fixed
- Fixed
Use
IdentityTransformStreamwhen proxying deferred HTTP response bodies. - Fixed
Remove noisy logs emitted while checking container and port readiness.
- Fixed
- New
Add return types to exported functions and public methods to satisfy ESLint and improve type checking.
- Fixed
Use the canonical
AlarmInvocationInfotype from@cloudflare/workers-typesfor thealarm()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#onErrorfromanytounknown. Subclasses that overrideonErrorcan still return any value. This should be a no-op for most users. - Fixed
Preserve original errors as
causewhen 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.
- New
- Fixed
Fix a race in
Containerwhere concurrentcontainer.fetchcalls 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
runningbut the underlying container has already exited. - Fixed
Fix subclass
sleepAfteroverrides being ignored during the initial activity timeout setup. Previously, the baseContainerconstructor calledrenewActivityTimeout()insideblockConcurrencyWhile()before subclass class-field initializers ran, so the firstsleepAfterMswas always computed from the base default ('10m') regardless of whether the subclass declaredsleepAfter = '2h'. A container could then be killed by the activity timeout before the subclass's longer window took effect on the nextrenewActivityTimeoutcall. Declarations like: - Fixed
Preserve Cloudchamber startup rate-limit errors in the Containers helper and return HTTP 429 from
containerFetch()when startup is rate limited.
- Fixed
- Fixed
Attach custom labels to your containers to help with observability and attribution. Set a
labelsproperty on yourContainersubclass, or passlabelsin thestartOptionsargument tostart()/startAndWaitForPorts(), and tag containers by tenant, environment, feature flag, canary cohort, or any other dimension you want to track. In local development, labels are visible on the underlying Docker container viadocker inspect.
- Fixed
- Fixed
Preserve response headers when proxying WebSocket upgrades through
Container.fetch().
- Fixed
- Fixed
Remove debug
console.log(props)statement fromContainerProxyinitialization
- Fixed
- New
Opt in to interceptOutboundHttps when interceptHttps = true
- New
3 other lines we could not sort, mostly version bumps
- 0.3.5
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.
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.