Changelog

v0.3.0

Upgrade PHP versions (first write action) · June 18, 2026

The app's first write action: upgrade a site's PHP version — and Search results become actionable.

Highlights

  • Upgrade a site's PHP version — press u on a site (Servers / Stacks / Search) to pick a version and apply it (PUT /sites/{id}/php). The upgrade event is tracked to completion.
  • Dynamic version picker — the offered versions come from the live endoflife.date PHP schedule (refreshed + cached), so new releases like 8.5 appear on their own; the current version is marked and EOL versions are flagged. Versions aren't filtered to "installed" — SpinupWP installs one on demand the first time a site uses it, so the full supported set is always offered.
  • Runs in the background — tracking lives in the app's store, so you can press Esc to close the modal and the upgrade keeps going. The site's row shows a spinner and the target version (→8.3) until it settles, then refreshes to the new version (or flags ⬆! on failure). Several sites can upgrade at once; the detail panel mirrors the in-progress state.
  • Search becomes a command surface — press Tab (or →) to hand focus from the search box to the selected result's action menu: o open · w SpinupWP · u PHP upgrade · h health. ← / Esc returns to typing.
  • Read-only-safe — writes need a Read/Write token. With a Read Only token an upgrade returns a clear "your token is read-only" message and nothing changes; the entire read path keeps working.

Notes

  • A site whose server has a pending SpinupWP platform upgrade can't be managed via the API until that runs — the picker is blocked and points you to the w web deep link.
  • This is the first write feature: the shared scaffolding (write-capable client, async event polling, confirm-before-firing overlay) is now in place to build the next write actions on.

View on GitHub →