fix(mysql): make sure migrations are run in order when run concurrently

Now we either lock all or none of the migrations to run,
to make sure they are not out of order when multiple instances of Emigrate run concurrently.
This commit is contained in:
Joakim Carlstein 2025-04-24 15:06:32 +02:00 committed by Joakim Carlstein
parent 6eb60177c5
commit 26240f49ff
13 changed files with 922 additions and 98 deletions

View file

@ -0,0 +1,5 @@
---
'@emigrate/mysql': patch
---
Make sure we can initialize multiple running instances of Emigrate using @emigrate/mysql concurrently without issues with creating the history table (for instance in a Kubernetes environment and/or with a Percona cluster).