The migration engine does not execute the last script when migrating

When migrating the database to a given version, the migration engine will not execute the last script. Most of the time, this is the version bump script. This means that the engine will report the migration as successful, but the reported database version will be incorrect, preventing the gateway from starting because of a version mismatch between the binary and the database. Furthermore, since the version reported by the database is incorrect, undoing the migration will not work either, meaning the database will be left in an unusable state with no way to fix it without a (thankfully simple) manual intervention on the database itself.