Release script that ensures the correct migration number is provided

[falexwolf]

Release script that ensures the correct migration number is provided

[falexwolf]

OK, so we can fix the current problem (see commit above) by manually removing the wrong migration that was written here:

https://github.com/laminlabs/lndb-setup/blob/409cccb2f0c1677da497db4277c16216f9db9e7d/lndb_setup/_db.py#L106-L108

We can avoid writing a migration number if there is any query result on the migration_XXXX table. This will avoid that there is ever a wrong migration number written.

Maybe we can avoid storing _migration completely, which would be great as we'd then eliminate all danger for error due to redundancy.

[falexwolf]

OK, so this should fix the issue for existing auto-migrating instances; the problem we just encountered:

• laminlabs/lamindb-setup#71

However, an inconsistent version string will still affect new instances, and make them impossible to migrate.

[falexwolf]

@fredericenard, could you rerun CI here after fixing the corrupted postgres instance?

• laminlabs/lamindb-setup#71

The PR seems to be good otherwise.

[sunnyosun]

@falexwolf Is this still needed?