Xavier Morel 1cb31cf2c2 [FIX] runbot_merge: 1.9 version & migration ... Forgot to bump the version when creating the migration. Also convert the migration to a single sql query, although the migration will never run because I ran the query manually to fix things up after finding out the data was "dirty" since the new code (assuming only modern statuses) was merged without running the migration. Thankfully it looks like the impact was not too severe (because the legacy statuses should only be present on very old commits / PRs), I don't remember when I deployed the update but apparently just a pair of PRs got affected, because their `previous_failure` was the old style and thus broke the "new failure" check.		2024-01-16 09:44:13 +01:00
..
13.0.1.1	[FIX] runbot_merge: statuses migration script should be for 13.0	2020-01-29 13:29:21 +01:00
13.0.1.2	[IMP] runbot_merge: make review rights repo-dependent	2020-02-11 08:07:57 +01:00
13.0.1.3	[FIX] runbot_merge: make github_login case insensitive	2020-02-11 09:17:52 +01:00
13.0.1.4	[ADD] runbot_merge: migration for repository status split	2020-07-14 13:34:05 +02:00
13.0.1.5	[CHG] runbot_merge: branch_ids -> branch_filter	2020-10-02 15:28:36 +02:00
13.0.1.6	[IMP] runbot_merge, forwardport: minor cleanups	2023-08-10 13:33:16 +02:00
13.0.1.7	[FIX] runbot_merge: add migration for draft column (#523)	2021-08-25 15:59:22 +02:00
15.0.1.8	[IMP] runbot_merge: split staging heads out to join tables	2023-08-10 14:04:59 +02:00
15.0.1.9	[FIX] runbot_merge: 1.9 version & migration	2024-01-16 09:44:13 +01:00