Viktor Szépe

<p>You get an email daily if there is some difference between WordPress.org’s Changelog page and readme.txt in SVN trunk.</p>
<h4>Only for development!</h4>
<h4>Features</h4>
<p>After activation a “Watch” link is added to each plugin. You may add there a plugin to watch for changelog differences. After clicking on “Watch” it toggles to Unwatch and vice versa.</p>
<h4>Activation</h4>
<p>The daily (wp-cron) cycle begins when you activate the plugin. The email is sent to the <strong>admin email</strong> address with subject <code>[<plugin-name>] Changelog mismatch</code>.</p>
<p>The email’s body is the first line (the latest release listed) of the SVN version and the WordPress.org Changelog page. You can write to plugins AT wordpress.org to correct the problem or wait for your next release.</p>
<h4>Links</h4>
<p><a href="https://github.com/szepeviktor/wordpress-plugin-construction/tree/master/plugin-changelog-checker" rel="nofollow ugc">GitHub repo</a></p>


Plugin changelog checker

Notifies you - the plugin developer - about WP.org not displaying changelog correctly.

Scott Cariss

<p>Automatic upgrades on live sites are, we think most people would agree, a Bad Idea. You can’t test them before they go live; they’ll play havoc with your version control system, if you’re using one; and if they fail or screw up, your live site is broken. Bad. Idea.</p>
<p>Enter Staunch. Staunch makes you stick to best practice for upgrades, by preventing even admins and superadmins from running WordPress’s automatic upgrade processes on your live site.</p>
<p>When you want to upgrade WordPress, you can do so on a local or development install of your site; after you’ve tested it and made sure everything’s okay, you can then deploy the site as you usually would — through version control, FTP, or something else.</p>


Staunch

A WordPress plugin to prevent automatic updates on your live sites.

Plugin changelog checker vs Staunch