Making the jump to 2.0.0 required a change to the database table schema that WP Mail Catches uses to save logs. An additional column is_html is added to improve the html detection of the emails being recorded.
Normally this column would be automatically added when the plugin is updated so the user won’t need to do anything and the plugin will continue to function as normal. However a few users have mentioned that the column was not added which caused the plugin to throw errors.
2.0.5 adds an additional button in the WP Mail Catcher settings page to allow the user to manually re-trigger the migrations (in this case just adding the is_html column) so it can attempt to add the column again.
I hope that answers your question!
