When a WordPress security release lands, you usually want it on every site now, not after a round of manual logins. This release makes that a couple of keystrokes: update core on one site, or on every site running a given version, with a canary site first.
Highlights
uis now Update. It opens a menu with PHP version (the flow you know) and WordPress core. The WordPress option checks the site over SSH with wp-cli and lists the versions you can move to, with the newest minor (security) release picked first. After you confirm, it runswp core update, then the database upgrade (network-wide on multisite), then reads the version back to verify. It keeps running if you close the overlay, and a toast reports when it's done.- Stacks groups WordPress sites by core version. Under Standard WP, Bedrock and Radicle, one row per version (
└ WP 7.0.2 51) shows who is still behind. The newest version in the fleet is highlighted. - Update a whole version group. Press
uon a version row:- It checks every site live first, because cached versions go stale as soon as sites update themselves.
- Then it shows a plan you can edit. The default target is the newest release in each site's own line (the low-risk security hotfix);
mswitches to the newest release overall, andspaceleaves a site out. - A canary site always updates alone first; if it fails, nothing else is touched.
- The rest follow up to 4 at a time, never two on the same server, and the run stops after 3 failures.
xstops starting new sites.
- Progress shows on the rows. A site that's updating shows
⠧ → WP 7.1.2, a failure leaves⬆!, and sites move into their new version row as they finish. - Bedrock and Radicle are included, with a warning. The update patches the files on the server, but
composer.lockstill pins the old version, so the nextcomposer install(a deploy, a clone) reverts it. The confirm screen names the pinned version, and bulk plans mark those sites⚙. Runcomposer updateand commit the lock to make it stick.
Fixed
- SpinupWP API errors say why. A rejected write used to show only "SpinupWP API error (HTTP 400)." It now includes the API's reason, such as which field it rejected.
- Version checks survive noisy plugins. Some plugins print PHP deprecation notices to stdout under newer PHP. That output buried wp-cli's update list, so a site two versions behind read as up to date. Core commands now run with plugins and themes unloaded, which also means a plugin that fatals can't block the core update that fixes it.
- Row versions stay current. Any version read by a check or an update now refreshes the version cached from the last
dprobe. - Failure toasts are red. They used to show a green ✓.
Notes
unow opens a menu first. Pressp(or Enter) to reach the PHP picker you're used to.- WordPress core updates use your SSH access as the site user, not the API token, so they work with a read-only token.