Documentation: the database migration tools Forklift and Flyway are abandonware about slick HOT 1 OPEN

Could you send a PR?

Notes:

1. Technically Forklift is probably still usable. The PRs aren't that important AFAIK. You may have to override sbt eviction errors but it should work. That said, I've never used it and don't know how many people have.
2. slick-migration-api is not a migration tool, but a way to express a migration action in terms of slick schemas. I don't recommend using it for an actual migration strategy, except with Forklift or something like it, because it creates a dependency cycle between the code and database that can result in being unable to compile the codebase. I don't have time to elaborate right now.
3. Flyway works perfectly fine with Slick, and so does flyway-sbt, even with current versions of Flyway. (One project of mine uses it and is on Flyway 9.3.1. I haven't checked 9.4.0 but it doesn't sound like you mean something broke that recently.) So should any other migration tool, like Liquibase or Play evolutions. For the most part migrations should be .sql files. But for code migrations I use the following to make it easy to work with Slick (maybe I should publish it as a library): https://gist.github.com/nafg/25b0cf942fbfe160e49b4939e1a61552

I assume the page you're talking about is https://scala-slick.org/doc/stable/migrations.html. A the bottom it says

The source code for this page can be found here.

You can click that link and edit the page in the browser to send a PR.

from slick.