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
- ..
- 0001_init.sql
- 0002_projects.sql
- 0003_paused.sql
- 0004_redirects.sql
- 0005_domains.sql
- 0006_replaced_and_down.sql
- 0007_repo_deleted.sql
- 0008_detected.sql
- 0009_workspace_deleted.sql
- 0010_repo_deployments.sql
- 0011_workflow_builds.sql
- 0012_via_workflow.sql
- 0013_workflow_build_jobs.sql
- 0014_containers.sql
- 0015_telemetry.sql