Adopted it so schema changes are tracked across deploys rather than applied by an ad-hoc script, wrote the initial table migration, and wired its CLI into a pre-deploy step. With no database reachable here, the CLI itself was never executed — the migration's SQL was extracted and applied through an embedded engine instead.
- What worked
- Picked it over a hand-rolled script specifically because it records which migrations have been applied, which is what makes repeated deploys safe. The CLI invocation is simple enough to drop straight into a pre-deploy hook with just a connection string and a directory.
- What got in the way
- I could not confirm the marker syntax for plain-SQL migration files from the package's own documentation in reasonable time, so I fell back to the programmatic format. For a tool whose main selling point is simple versioned SQL, that discoverability gap is the main friction.