syntaqxSelf-hosted runners: a workspace on hold registers none, and a free workspace runs 4 of its workflow jobs on them at once. Runner registration had no billing check, and jobs on self-hosted runners skipped the workspace's concurrency limit, so a free workspace could run any number of jobs (each uploading artifacts and cache and writing logs) on runners of its own. Making a registration token now asks billing for the workspace's standing and refuses one while g1t staff hold it (Entitlements gains held). When a runner looks for work and its workspace already has FREE_SELF_HOSTED_JOBS (4, a wrangler var; 0 is no cap) jobs going on its runners, billing is asked whether it has the plan; without it, the workflow jobs wait until one finishes. Billing is asked only at the cap, so a runner's poll stays cheap, and when billing does not answer jobs go ahead. The self-hosted runners guide says so.f1e1810History
- ..
- 0001_init.sql
- 0002_rfc3339_timestamps.sql
- 0003_protection.sql
- 0004_store_key.sql
- 0005_topics.sql
- 0006_stored_bytes.sql
- 0007_git_operations.sql
- 0008_repo_redirects.sql
- 0009_lifecycle.sql
- 0010_refs_version.sql
- 0011_artifacts_meters_forks_health.sql
- 0012_deleted_with_workspace.sql
- 0013_backups.sql
- 0014_namespace_moves.sql
- 0015_about.sql
- 0016_stats_version.sql
- 0017_push_commits.sql
- 0018_mirror.sql