Any recommended workflows for running database migrations after upgrading Kratos version, without downtime? Seems like if Kratos will have problems if you run migrations for the new version before updating, but also if you start the newer version before running migrations? I get that the migrations are fast, just looking to minimise steps

hi there, we would either recommend a full A/B switch (which would require a second DB), or a full switch (Version N serves traffic, run migration as a side procedure like a job, switch version to N+1)

thanks for that. Does Ory have any policy about whether database migrations for new versions break compatibility with the previous version? ie - does Kratos 0.13 stop working with the Kratos 1.0 database schema?

each version has their own migrations ands migration history, so a v1 db with all migrations applied could have modified the db enough for 0.13 to not work properly