Automatic updates create a new problem for plugin authors. Users no longer have to download and install a plugin, and in the process see what has changed, they now just update it and hope it all works out. My question today is, what should plugin authors do if they know the latest update is liable to break things?

One option is to release an intermediate version. A version which contains a warning message that the next version will have major changes and so users shouldn’t update without thinking things throught first.

Another options if to bundle a previous version of the plugin. The they can either upgrade but ask the user if they want to go back, or alternatively explain the changes and then ask the user if they want to proceed with them.

Lastly, they could simply prepare to field the inevitable support queries and hope enough users read the updates page before going ahead.

I am still trying to decide which option to go for with some changes to one of my plugins.

Do you ugrade without checking the changes? I know I tend to. If so which option do you prefer? or is there something I have missed?