@@ -12,7 +12,7 @@ without churning under them. |
| 12 | 12 | |
| 13 | 13 | ## SQL schema |
| 14 | 14 | |
| 15 | | -Actions migrations currently span 0042–0051, 0053, 0057, and 0060. |
| 15 | +Actions migrations currently span 0042–0051, 0053, 0057, 0060, and 0064–0066. |
| 16 | 16 | Migration 0052 belongs to the repo source-remotes feature, 0054 |
| 17 | 17 | belongs to push event protocol tracking, 0055 belongs to the social |
| 18 | 18 | feed, 0056 belongs to user profile contribution settings, 0058 belongs |
@@ -33,6 +33,7 @@ to repo name reuse, and 0059 belongs to GitHub org imports. |
| 33 | 33 | | 0053 | `runner_jwt_used` | Single-use replay gate for runner job JWTs | |
| 34 | 34 | | 0057 | `workflow_job_secret_masks` | Encrypted claim-time log mask snapshots per job | |
| 35 | 35 | | 0060 | Actions retention indexes | Narrow cleanup indexes for terminal steps/runs | |
| 36 | +| 0066 | `actions_*_policies`, `workflow_run_approvals` | Enablement, runner-pool caps, and approval decisions | |
| 36 | 37 | |
| 37 | 38 | A few load-bearing choices, called out so they're easy to spot in a |
| 38 | 39 | later schema diff: |
@@ -77,6 +78,14 @@ later schema diff: |
| 77 | 78 | claim time, preventing a rotated or deleted secret from disappearing |
| 78 | 79 | from server-side masking while the old value is still in a runner's |
| 79 | 80 | job payload. |
| 81 | +- **`actions_site_policy`, `actions_org_policies`, |
| 82 | + `actions_repo_policies`** — inherited Actions enablement and abuse |
| 83 | + caps. Runner claim and trigger enqueue both read the effective policy: |
| 84 | + repo override, then org override, then site default. |
| 85 | +- **`workflow_run_approvals`** — one approval-decision row for every run |
| 86 | + whose `workflow_runs.need_approval` flag is set. Approval records the |
| 87 | + maintainer and lets runner heartbeats claim the existing queued jobs; |
| 88 | + rejection completes the run with `action_required`. |
| 80 | 89 | |
| 81 | 90 | The `version` and `run_index` patterns are the two pieces I'd point |
| 82 | 91 | out to a future maintainer first. Both are cheap to add now and |