I'm not sure what would've caused it this round, but I have seen it happen before.

It usually only happens when a migration isn't backwards compatible but afaik there shouldn't be one in this case.