syntaqxA deploy that changes the runner's image or its container settings rolls every idle sandbox over at once (--containers-rollout=immediate), where Cloudflare's default rollout went in steps over wall-clock time and, with deploys often half an hour apart, never reached every sandbox: jobs kept starting on old images and old machine sizes. A change to the container settings alone, such as the instance type, now rolls out too; before, an unchanged image meant --containers-rollout none and the new settings were never applied. Busy sandboxes still get rollout_active_grace_period to finish.e277e3fHistory
- ..
- access.test.ts
- access.ts
- cloudflare.ts
- containers.flow.test.ts
- containers.test.ts
- containers.ts
- custom-hostnames.ts
- domains.ts
- environments.test.ts
- environments.ts
- hostname.test.ts
- hostname.ts
- index.ts
- metering.test.ts
- metering.ts
- moves.flow.test.ts
- moves.test.ts
- moves.ts
- names.test.ts
- names.ts
- redirect.test.ts
- redirect.ts
- repo-deployments.ts
- retries.test.ts
- retries.ts
- telemetry.test.ts
- telemetry.ts
- workflow-builds.flow.test.ts
- workflow-builds.test.ts
- workflow-builds.ts