Where are Hasura migrations stored in DB / server?

[joanrodriguez]

• I have a Hasura project with 3 environments: local, staging and prod
• In order to develop locally with the latest data from PROD, I have written a script that dumps and restores PROD db locally
• However, when trying to migrate the locally restored PROD db, I run into issues because the migration state is corrupted. Some migrations have been ran on PROD but they appear as not ran locally although it is exactly the same db.
• When running hasura migrate status against PROD and local, I do see different results indeed
• However when inspecting the table hbd_catalog.schema_migrations on PROD and locally it contains exactly the same data...

What's even more confusing is that although PROD correctly marks some of my migrations as ran, their timestamp is not present in the migration table on PROD db...

Then when I run hasura migrate apply --version 1629372456821 --skip-execution the migration is correctly marked as done but no new row is added to hbd_catalog.schema_migrations...

Is there some other place that Hasura uses to keep track of these migrations?