What happens
Follow-up to #5059/#5060 (merged): widenGithubIdColumnsToBigint's first pass grepped migrations/*.sql for CREATE TABLE column-list definitions only. Two GitHub-native-id columns were added later via single-line ALTER TABLE ... ADD COLUMN ... INTEGER statements (migrations 0071, 0077) and were missed by that grep pattern:
installations.app_id -- GitHub's own numeric App id.orb_github_installations.account_id -- the installation owner's numeric GitHub account id.
Found via a direct information_schema.columns query against the live edge-nl-01 schema for every remaining integer id-shaped column, run as a final sanity check after the first fix merged.
Fix
Add both to GITHUB_ID_BIGINT_WIDENING_SQL in src/selfhost/pg-adapter.ts, same idempotent Postgres-only pattern as #5060. Both statements were dry-run validated then applied directly against edge-nl-01 (same urgency reasoning as #5059: the underlying overflow is a live risk class, not hypothetical).
What happens
Follow-up to #5059/#5060 (merged):
widenGithubIdColumnsToBigint's first pass greppedmigrations/*.sqlforCREATE TABLEcolumn-list definitions only. Two GitHub-native-id columns were added later via single-lineALTER TABLE ... ADD COLUMN ... INTEGERstatements (migrations 0071, 0077) and were missed by that grep pattern:installations.app_id-- GitHub's own numeric App id.orb_github_installations.account_id-- the installation owner's numeric GitHub account id.Found via a direct
information_schema.columnsquery against the live edge-nl-01 schema for every remainingintegerid-shaped column, run as a final sanity check after the first fix merged.Fix
Add both to
GITHUB_ID_BIGINT_WIDENING_SQLinsrc/selfhost/pg-adapter.ts, same idempotent Postgres-only pattern as #5060. Both statements were dry-run validated then applied directly against edge-nl-01 (same urgency reasoning as #5059: the underlying overflow is a live risk class, not hypothetical).