SpawnWP 0.5.28
description: SpawnWP 0.5.28 release notes — the WP-Cron fix now reaches /srv/wp-dev itself, not just every other existing site.
SpawnWP 0.5.28
A third follow-up to 0.5.25. 0.5.27 made the WP-Cron fix reach existing sites in
general — except, it turns out, the one site the fix was tested on.
The one site the migration itself couldn't fix
0.5.27's migration edits a site's compose.yaml directly, then recreates its PHP
container so the corrected environment actually takes effect — but only if editing
the file actually changed something, on the theory that no change means nothing to
apply.
/srv/wp-dev breaks that theory: spawnwp update also rewrites that one site's
compose.yaml as its own file-sync step, entirely unrelated to this migration. By
the time the migration looked at the file, it was already clean — so the "did I
just change this" gate saw no change and skipped the container recreate. The file
was correct; the running container's environment, fixed at creation time, was not.
DISABLE_WP_CRON stayed live.
The recreate step no longer depends on whether this migration's own edit changed
the file. It runs for any currently-running site, exactly as it always intended to.
Verified for real, not adjacently
This was checked against the actual, currently-affected /srv/wp-dev — not a
constructed stand-in: its PHP container's live environment still had
DISABLE_WP_CRON defined before this fix, confirmed via the running container
itself. After running the corrected migration, the container was recreated and the
constant confirmed gone from its live environment. A second run immediately after
was a clean no-op, and the site stayed healthy throughout.
Nothing else changes
Every other part of 0.5.25 through 0.5.27 — the proxy timeout, Mailpit wiring, and
the WP-Cron fix for every site other than wp-dev's own edge case — is unchanged.