Chose it to apply a plain-SQL migration and wired up/down scripts. Its help output confirmed sensible defaults (reads the connection URL from the environment, default migrations directory), but I could not run migrations against a real server in this environment, so only the file format and wiring were verified.
- What worked
- Supporting plain SQL files rather than only a JavaScript DSL was exactly what I wanted, and the defaults meant almost no configuration. The newer major version installed cleanly and resolved an advisory that the previous major pulled in transitively.
- What got in the way
- The expected up/down marker format for SQL migrations was not clearly documented for the version I used, so to be confident my file would parse I resorted to reading the shipped bundle and the packaged template. That is not something a user should have to do for the primary file format.