WP Pusher 3.0.19: no more plugins deleted by double deploys

WP Pusher 3.0.19 is out. It fixes plugins getting deleted when two deploys run at once, raises the minimum WordPress and PHP versions, and starts the groundwork for deploy reports.

One deploy per package at a time

If two deploys of the same plugin or theme arrived in the same second, both of them ran at once, and each one replaced the package’s folder while the other was still writing into it. That could happen with a repository wired up to more than one webhook, a single push that fans out into several deploys, or an impatient second click of the Update button. You’d see “Filesystem error” in the log, and the plugin had either vanished or deactivated itself.

Starting with 3.0.19, WP Pusher deploys one version of a package at a time. If a deploy is already running, a second deploy of that same package is skipped and noted in the log (“Skipped a deploy of ...”) instead of running alongside it. Deploys of different packages still run side by side, the same as before.

If that skipped line shows up for you regularly, I’d check whether your repository has two webhooks pointing at the same site. It’s harmless now, but it’s worth tidying up.

New minimums: WordPress 6.0 and PHP 7.4

3.0.19 needs WordPress 6.0 or newer and PHP 7.4 or newer, and it’s tested up to WordPress 7.1. WordPress will still offer the update to sites below those versions, so check yours before you update. You’ll find both under Tools → Site Health → Info.

See which commit reached each site

This release also lays the groundwork for deploy reports. Each instance of WP Pusher can now tell your WP Pusher dashboard which commit each site has deployed, and when. That lets you (or a coding agent working on your behalf) check whether a push actually reached a site without logging into wp-admin.

It’s off unless you turn it on, and the dashboard side isn’t switched on yet, so right now no site sends a report.

While reporting is on, a site sends a report when a plugin or theme is installed or updated, plus the full list of its WP Pusher packages every twelve hours. It never includes file contents, and it never includes your GitHub, Bitbucket or GitLab credentials.

If you want the full picture, the plugin’s readme has a new section called “What WP Pusher sends to wppusher.com” that lists everything and why, and our privacy policy covers the same ground.

Updating

Update from the Plugins screen like you would any other plugin. 3.0.19 also cleans up the license-checking code, and every change is listed in our changelog. If anything looks off after you update, email me at hi@wppusher.com. I read every one.

← All posts