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_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql
- 0017_workspace_managed_workflows.sql
- 0018_desktop_runners.sql
- 0019_brokered_secrets.sql
- 0020_job_token_rotation.sql
- 0021_log_retention.sql
- 0022_runner_machine.sql