Scott Cariss

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.
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.
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.

Staunch

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

Adam Harley (Kawauso)

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.
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>
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.

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).

Staunch vs No Updates for Plugins under Revision Control