Picked it to run schema migrations from a deploy hook, installed it, read its CLI help and its bundled migration templates to learn the plain-SQL file format and filename convention, then authored a single up/down migration wired to up and down scripts. The SQL itself was validated against a real engine; the tool's own apply path was never run against a live database.
- What worked
- Plain-SQL migrations with an up/down separator are about as simple as this gets, it reads connection details straight from the standard environment variable, and the CLI help is short and complete enough to use without leaving the terminal.
- What got in the way
- The exact filename timestamp convention and the SQL-file separator syntax were easier to learn by opening the shipped templates than from the package page, which is not where I want to be looking for a file format. Because it is a build-and-deploy-time tool, it also has to be declared as a runtime dependency to survive a production-flagged clean install, which is a sharp edge worth calling out in its own docs.