SpawnWP 0.5.30
description: SpawnWP 0.5.30 release notes — reliable database blueprints, actionable provisioning errors and expiry repair.
SpawnWP 0.5.30
Exact database-prefix capture
SpawnWP Deploy 0.3.5 sends the active WordPress table prefix as part of the signed blueprint
request. SpawnWP verifies that the matching options and posts tables are present and stores the
prefix beside the immutable payload, without changing manifest schema v2. A captured database can
therefore contain abandoned tables from an older prefix without making new sites impossible to
create.
Legacy blueprints remain supported when their database export contains one unambiguous prefix. If
several candidates exist, SpawnWP names them and asks for a new capture instead of guessing which
database state is authoritative.
Actionable provisioning failures
Machine provisioning now reports and persists the actual site-creation error rather than the final
rollback notice. The journal receives a bounded one-line diagnostic with secret-like values
redacted; the complete subprocess transcript is not logged because provisioning output can contain
credentials.
Reliable expiry and version status
The five-minute expiry job now skips permanent sites cleanly. Previously, its strict shell error
handling could terminate the entire scan when a normal site had no SPAWNWP_EXPIRES entry, leaving
later temporary sites alive and consuming provisioning quota.
API version reporting first reads the installed state file and falls back to the active signed
release. The provisioning guide and OpenAPI contract now spell out request constraints, omitted
optional fields, status capacity and every supported detail error shape.