1. Weston Ruter

    If I understand correctly, the email confirmations get sent out to all plugin committers correct? It’s not just sent to the WordPress.org user who is the owner of the plugin, right? I can see that being a desirable security setting as well, if only the owner can approve a release, rather than any one or multiple committers.


    • Dion Hulse

      Yes, the email goes out to all committers.

      To give an example, if CommitterA commits a release CommitterA, CommitterB, or CommitterC can confirm the release.

      There’s also an option to enable multiple confirmations, for example: A commits a release, and A+B, A+C, or B+C must approve it before it’s released.
      This currently requires contacting the plugins team to enable as it hasn’t been as thoroughly tested, and is not what most plugin authors would want to “accidentally” enable.


  2. Weston Ruter

    Also, is it only the auto-updates that are held up until email confirmation is received? Or is it that the release is held up entirely, even for users who have automatic updates turned off? In other words, is it an auto-update lock or a SVN lock?


    • Weston Ruter

      Ah, no, it’s unrelated to auto-updates. It’s basically an SVN tag lock. I enabled for the PWA plugin and got the initial email:

      Howdy Weston Ruter,

      Release confirmations are now enabled for PWA.

      This means that each time you release a new version of PWA you’ll be required to confirm the release by following a link in an automated email.

      For more information, please read the following handbook article:


  3. Rodney Brazil

    Curious to know the “high usage” threshold. With such a wide range of usage, this could mean anything.


Comments are closed.

%d bloggers like this: