chore(db): renumber duplicate-numbered migrations #134

Merged

gmackie merged 1 commit from chore/renumber-dup-migrations into main

2026-07-23 18:58:36 +00:00

gmackie commented

2026-07-23 18:44:46 +00:00

Owner

Three migration numbers had collisions (0029 ×2, 0050 ×2, 0062 ×3), leaving lexical apply order ambiguous for fresh installs and future tooling. This follows the existing 0030a_ precedent: the chronologically older file keeps the bare number, later ones get letter suffixes (a sorts after _, so ordering stays correct).

before	after
`0029_harsh_rage.sql`	`0029a_harsh_rage.sql`
`0050_far_stick.sql`	`0050a_far_stick.sql`
`0062_preflight_core_schema.sql`	`0062a_preflight_core_schema.sql`
`0062_preflight_dev_sessions.sql`	`0062b_preflight_dev_sessions.sql`

Renames only — all of these are already hand-applied to production; no SQL content changes and no operator action needed. Only code reference to any migration filename is agent/internal/cmdexec/run_migration_test.go (a different file, untouched).

🤖 Generated with Claude Code

Three migration numbers had collisions (**0029 ×2, 0050 ×2, 0062 ×3**), leaving lexical apply order ambiguous for fresh installs and future tooling. This follows the existing `0030a_` precedent: the chronologically older file keeps the bare number, later ones get letter suffixes (`a` sorts after `_`, so ordering stays correct). | before | after | |---|---| | `0029_harsh_rage.sql` | `0029a_harsh_rage.sql` | | `0050_far_stick.sql` | `0050a_far_stick.sql` | | `0062_preflight_core_schema.sql` | `0062a_preflight_core_schema.sql` | | `0062_preflight_dev_sessions.sql` | `0062b_preflight_dev_sessions.sql` | **Renames only** — all of these are already hand-applied to production; no SQL content changes and **no operator action needed**. Only code reference to any migration filename is `agent/internal/cmdexec/run_migration_test.go` (a different file, untouched). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

gmackie added 1 commit

2026-07-23 18:44:46 +00:00

chore(db): renumber duplicate-numbered migrations

forgegraph/ci CI passed

CI / ci (pull_request) Successful in 8m18s

Details

75782854a8

Three migration numbers had collisions (0029 x2, 0050 x2, 0062 x3),
leaving lexical apply order ambiguous for fresh installs and future
tooling. Follow the existing 0030a_ precedent: the chronologically
older file keeps the bare number, later ones get letter suffixes
(suffix sorts after underscore, so ordering stays correct).

Renames only — every one of these is already applied to production
by hand; no SQL content changes, no operator action needed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

gmackie merged commit c58f60c457 into main

2026-07-23 18:58:36 +00:00

gmackie referenced this pull request from a commit

2026-07-23 18:58:36 +00:00

Merge pull request 'chore(db): renumber duplicate-numbered migrations' (#134) from chore/renumber-dup-migrations into main

gmackie referenced this pull request from a commit

2026-08-23 22:11:28 +00:00

docs(todos): correct the migration-collision note

gmackie referenced this pull request from a commit

2026-08-23 22:29:17 +00:00

docs(todos): correct the migration-collision note