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_lifecycle.sql
- 0003_repo_settings.sql
- 0004_up_to_date.sql
- 0005_assignees.sql
- 0006_merge_rules.sql
- 0007_timeline.sql
- 0008_plans.sql
- 0009_lifecycle_snapshot.sql
- 0010_merge_queue.sql
- 0011_agent_messages.sql
- 0012_exchanges.sql
- 0013_commit_statuses.sql
- 0014_mergeability.sql
- 0015_agent_runs_and_memory.sql
- 0016_by_author.sql
- 0017_agent_mentions.sql
- 0018_guardrails.sql
- 0019_memory_capture.sql
- 0020_agent_waits.sql
- 0021_confidence.sql
- 0022_required_checks.sql
- 0023_read_paths.sql
- 0024_g1t_name.sql
- 0025_requested_by.sql
- 0026_code_owners.sql
- 0027_labels_milestones_bases.sql
- 0028_rulesets.sql
- 0029_commit_checks.sql
- 0030_comment_edits.sql
- 0031_mention_revisions.sql
- 0032_contributions.sql
- 0033_agent_comments.sql