ThibG b194caade4 Fix old migrations failing because of strong_migrations update (#12692) ... Fixes #12690 The `strong_migrations` update from f673e3d120 introduced a check for `change_column_null` specific to Postgres. This rejects old migrations. This commit just wraps old migrations with `safety_assured` to bypass this check. Alternatives would have been to: - Disable that check entirely (a possibility added in that same `strong_migrations` version) for Mastodon, but it makes sense to write new migrations without such a strong lock. - Rewrite the old migrations to do it in a way that do not require an exclusive lock. I thought fixing those old migrations for performance wasn't worth the pain. Also, if I understand correctly, the next version of `strong_migrations` is going to include a helper to do that. We could update those migrations at that point.		2019-12-29 05:39:08 +01:00
..
migrate	Fix old migrations failing because of strong_migrations update (#12692)	2019-12-29 05:39:08 +01:00
post_migrate	Validate Web::PushSubscription (#11971)	2019-09-27 15:24:13 +02:00
schema.rb	Increase max backup size (#12602)	2019-12-17 13:30:58 +01:00
seeds.rb	Change unconfirmed user login behaviour (#11375)	2019-07-22 10:48:50 +02:00