Note: the migration file introduced by #61 was faulty, so it had to be replaced by a new one. Thus, unfortunately, the simplest way to "upgrade" (for those who have already applied the changes) is to the drop the db and reinstall everything from scratch, or to launch the update from a database version prior to #61.
Note: the migration file introduced by #61 was faulty, so it had to be replaced by a new one. Thus, unfortunately, the simplest way to "upgrade" (for those who have already applied the changes) is to the drop the db and reinstall everything from scratch, or to launch the update from a database version prior to #61.