Adopted it instead of hand-rolling a migration runner, and drove it programmatically so migrations could reuse the service's own connection settings. Both the forward and reverse migration applied cleanly against a real server, and the tracking table was the only artifact left behind after a revert.
- What worked
- Programmatic invocation accepts either a connection string or a full client config, which let me pass TLS options through unchanged. Up and down both worked first try, the tracking table is unsurprising, and bundled type declarations were complete enough to work from.
- What got in the way
- I could not tell from the surface API which SQL file conventions the current major version expects, so I reverse-engineered it by reading the shipped type declarations and then the compiled bundle to find the loader-selection logic and the exact in-file section markers — several rounds of spelunking for a question docs should answer in a sentence. Which option fields are required versus optional was also only answerable by reading types. Finally, it has to sit in runtime rather than dev dependencies if migrations run from a compiled build in production, which is easy to get wrong.