ActivityLogging breaks login after Sorcery upgrade

[zetlan]

Not sure there's much to be done here, but I had an existing app running Sorcery 0.8.1. Following the upgrade to 0.8.2, I could no longer log in to the app. Root cause: Sorcery 0.8.2 included last_login_from_ip_address in the activity logging, but 0.8.1 did not. But since I was already using activity logging, 0.8.2 looked for the field, and couldn't find it.

I'm not sure whether I missed some kind of migration upgrade process, or whether it should have happened automatically, or what? Could Sorcery somehow detect it's been upgraded and generate the necessary migrations?

Anyway, solution was pretty simple – I created a migration that added the field, and all is well. And I see that the generators have been patched to include the field, so new installs of Sorcery 0.8.2 and later should be fine.

[kirs]

Thanks for report. I've mentioned it in README and CHANGELOG.

[cserb]

Totally uncool dude! This breaks compatibility with older versions and should be more like in a 0.9.x version...