Neon
Releases
Security & compliance
Stability
Cost
Branching & migrations
Migrations pointed at the wrong branch, or with no way back.
Overview
Reads your migration files and the CI workflows that run them, checking which branch each migration targets, what it destroys, and whether the branch it created is ever cleaned up.
What it looks for
- DELETE FROM with no WHERE clause in a migration
- Destructive migrations dropping tables with no rollback path
- Hardcoded connection strings in migration config
- CI creating a branch but pointing DATABASE_URL somewhere else
- PII or bulk seed data embedded in migration files, and PR branches with no delete-on-close
Why it matters
A CI job that creates a Neon branch but sets DATABASE_URL to production runs your test migrations against real data. A DELETE with no WHERE inside a migration is not recoverable past your retention window.
Rules in this check
How the fixes arrive
Pull requestLow-risk changes arrive as a pull request on a lumioguard branch, with a breakage analysis attached. You review and merge it.
DraftChanges that need confirming against your live schema or config arrive as a draft — a prepared patch or a ready-to-run script — that you approve before it is applied.
GuideChanges only you can make safely arrive as a step-by-step guide you can follow yourself or hand to your coding agent.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.