You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, the default for go-migrate is to pull db migrations directly from Github (main branch) and run them (including with the autoMigrate flag). This means that you could potentially have a mismatch between the migrations being run and the server code if it is not up to date.
Expected behavior
Only the migrations up to the current version of source (whether built locally or pre-built) should run. This might mean packaging the migrations along with the binary.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, the default for go-migrate is to pull db migrations directly from Github (main branch) and run them (including with the
autoMigrate
flag). This means that you could potentially have a mismatch between the migrations being run and the server code if it is not up to date.Expected behavior
Only the migrations up to the current version of source (whether built locally or pre-built) should run. This might mean packaging the migrations along with the binary.
The text was updated successfully, but these errors were encountered: