Create a migration validation script for production database schema drift

[success-OG]

Labels: backend infrastructure database

Background
scripts/validate-migrations.ts (2.7 KB) checks that migration files are ordered correctly but does not compare the actual DB schema against what the migrations should have produced. Schema drift (direct DB edits in staging accidentally applied to prod) is undetectable.

What "Done" Looks Like

• Script connects to the target DB and runs pg_dump --schema-only
• Compares the dump against the expected schema derived by running all migrations on a fresh DB
• Reports any columns/tables/indexes present in the DB but absent from the migration history (and vice versa)
• Runnable as npm run validate:schema -- --env production
• Non-destructive: read-only DB connection

[aliyuHabibu]

@aliyuHabibu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'm a software engineer. I have gone through the issue and I can resolve it, assign it to me. Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @aliyuHabibu to this issue.

[mukadasamos]

@mukadasamos has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer, Please assign me to this issue. Thanks for your consideration

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mukadasamos to this issue.

[nikkybel]

@nikkybel has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please can i work on this?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nikkybel to this issue.

[Okorie2000-code]

@Okorie2000-code has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I will love to work on this issue. Please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Okorie2000-code to this issue.

[vrickish]

@vrickish has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @vrickish to this issue.

[studiomonkeyx]

@studiomonkeyx has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

pls let me work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @studiomonkeyx to this issue.

[drips-wave]

Congratulations, @nikkybel! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @nikkybel: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊