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.

Adam Harley (Kawauso)

<p>Checks for the presence of the <code>.svn</code> directory in each plugin’s directory. Disabled for plugins with their files directly in the <code>/plugins/</code> directory to prevent false positives.</p>
<p>Also supports other systems through the use of the <code>REVISION_CONTROL</code> constant. Just set this to the directory created by your revision control system in your <code>wp-config.php</code></p>
<p>Based on <a href="http://developersmind.com/2010/06/12/preventing-wordpress-from-checking-for-updates-for-a-plugin/" rel="nofollow ugc">code</a> by PeteMall.</p>


No Updates for Plugins under Revision Control

Prevents plugins from being updated by the WordPress updater if they are under Subversion revision control (or other systems).

Plugin changelog checker vs No Updates for Plugins under Revision Control