Protect The Shire holds plugin updates for hours. ToggleWP now watches the queue for you, and can check releases while they wait

In June, WordPress.org started holding every new plugin release for a while before it is offered to sites. It calls this Protect The Shire. The idea is a good one: if a plugin author’s account is hijacked and a malicious release goes out, the hold gives WordPress.org time to spot it before it reaches millions of sites.

The hold started at 24 hours. Patchstack measured it falling to about six and a half hours in July. It applies to every release, including ones that fix a security hole.

That last part matters to agencies. When a plugin author ships a security fix, the fix is public. Anyone can compare the old version with the new one to see what was wrong. Meanwhile your sites can’t install it, because WordPress.org isn’t offering it yet. Then, once the hold ends, each site still only notices the update at its next 12-hourly update check.

ToggleWP Cloud now helps with both parts of that wait.

For everyone: sites hear the moment the hold ends

Every 10 minutes, ToggleWP Cloud checks wordpress.org for new releases of plugins your sites run. For each one, it asks WordPress.org’s update service the same question your sites ask: “is there anything newer?” While the release is on hold, the answer is no. As soon as WordPress.org starts offering it, ToggleWP Cloud tells your sites that run the plugin. They hear at their next hourly check-in, or within seconds if you use instant pings.

ToggleWP never tells a site about a release before WordPress.org offers it. This doesn’t shorten the hold, it just stops your sites waiting up to another 12 hours after it ends. It’s on for every agency with no setup.

While a security fix is on hold, your security update email says so: “On hold at WordPress.org since 09:12 UTC; your sites are told as soon as it’s released.”

Opt in: let ToggleWP check a release while it’s on hold

Some agencies would rather not wait for the hold at all when it’s a security fix and the change can be checked.

A release on hold can already be downloaded from wordpress.org. So ToggleWP Cloud can now:

  1. Download the held release, and the version your sites are offered now,
  2. Scan what changed between them with Update Guard, the same checks we use on premium plugin updates,
  3. Offer releases that pass straight away to sites whose policy allows it.

Update Guard’s checks look for:

  • Files already known to be malicious,
  • Suspicious code such as obfuscated payloads, shell commands, hidden files and new admin accounts,
  • Changes to the plugin’s author or update details.

Anything that scores above low risk is reviewed by AI before it can pass. A high-risk change needs a confident “clean” verdict, so if there’s any doubt, the release isn’t offered early and your sites wait for WordPress.org as usual.

What your sites do with it

The release is added to WordPress’s own list of available updates, so your existing settings still decide what happens:

  • Automatic updates on for that plugin: it installs within minutes.
  • Automatic updates off: it shows in wp-admin as an update, ready for you or your client.

Before installing, the site checks that the file it downloaded is exactly the one ToggleWP Cloud scanned. If it isn’t, the update is refused, even when someone clicks Update by hand. Only the official wordpress.org download for that exact plugin and version is accepted.

If something goes wrong

ToggleWP Cloud keeps checking a release it has offered early. It is withdrawn if:

  • WordPress.org removes or replaces that version,
  • The plugin is closed on wordpress.org, or
  • A file in it is later found to be malicious.

Once withdrawn, no more sites are offered it. If any of your sites already installed it, you get an email listing exactly which ones, so you can check them and put the previous version back.

Why it’s off by default

Protect The Shire exists for a reason. A hold gives WordPress.org’s own checks time to catch a hijacked release. Installing early means trusting ToggleWP’s scan in place of that wait, and no scan is perfect.

For many sites that’s the right trade, especially for security fixes on popular plugins. For others, such as a client who’d rather wait, or a site where stability matters most, it isn’t. So it’s your choice, site by site.

How to turn it on

Early releases is a setting in the Vulnerability Monitor policy, so it can be different for each policy profile. For example, you could turn it on for the sites you host yourself and leave it off for everything else.

  • Off (the default): wait for WordPress.org.
  • Security fixes only: only releases that fix a known vulnerability, or whose release notes ToggleWP Cloud has judged to be a security fix.
  • All releases: any held release that passes the scan.

You’ll need:

  • Update Guard in your ToggleWP Cloud plan, since early releases use its scanner,
  • ToggleWP 2.0.5 or later on your client sites.

In short

  • WordPress.org now holds plugin releases for hours, security fixes included.
  • ToggleWP Cloud watches the hold and tells your sites the moment a release comes out, for every agency, with nothing to set up.
  • If you opt in, ToggleWP Cloud also scans held releases and offers the ones that pass straight away, checks every download matches what was scanned, and emails you if a release it offered is later withdrawn.
  • It’s off by default, because skipping the hold is a trade-off your agency should choose.

Similar Posts