@cloudflare/containers
0.3.7 · 4 Jun 2026MIT OR Apache-2.03M / weekRepositoryHomepagenpmAtom feed
Upgrading @cloudflare/containers From 0.3.3 to 0.3.4
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 4
- fixes
Release by release
- 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
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.