Automatic migrations in case of outdated version found in migration_scheme.

I have studied issues as far as I could, but I haven't found an answer to my question, sorry in advance if I was inattentive.

How can I implement the following task:

When the application is launched, the version of the last added migration file and the version in the database schema should be checked.
If they do not match, load all migrations from files starting with the version specified in the database.

Is it possible with tern now?

p.s. thank you very much for your efforts

The issue names no files, tests, or entry points; begin by locating tern's application-startup path and its migration and database-schema version handling. Done would mean detecting a version mismatch at launch and loading migrations beginning with the version recorded in the database.

Written by the indexing model from the issue text.