I disagree. Your library is not in control of the users database, your users are and need to be. You can provide the “what needs to change”, but your users need to be able to control when those changes happen and at which cadance. E.g. they might be at V2 of your libraries db schema, while V5 is latest. Users might want to move to V5 directly or they might have lots of data and want to move one version at a time. There might be other changes in their db schema related to changes in your library. And in the end to me the most important part of migrations is that I can look into one folder and see all the changes applied to my database.

You can take a look at how Oban handles migrations. On a general note you wouldn’t bundle migration scripts, but your library would include apis for users to call in their own migration scripts.