Skip to content
How to install

PHP updates

A site runs the PHP release in its server’s site image, such as 8.4.27. When PHP publishes a patch release, each server gets a new image with it, and every site moves onto it. Nobody has to start anything.

The Overview's PHP card: the PHP release each version's sites run, and one site still on an older PHP than a security release

The PHP card on the Overview has a line for each PHP version your sites run. While some of a version’s sites are on an older release than its newest, the line says how that release is reaching them. Sites hosted elsewhere are not counted, because WPL7 does not run their PHP.

Line When
3 sites run PHP 8.4.28 None of them is on an older release. The dot stays gray until the panel knows they run the newest.
PHP security release on Wed 21 Oct, 14:00 UTC php.net has announced a security release ahead of time
PHP 8.4.28 is out. Waiting for its image. The release is out, and no server has its image yet
Updating sites to PHP 8.4.28: 5 of 12 Sites are moving onto it
2 of 12 sites still on an older PHP than 8.4.28 Those sites did not move. The line’s details say why.
Next: PHP 8.4.28 and 8.5.13, expected Thu 19 Nov A release candidate is out, and its release is due within a week

A line opens the details of its PHP version: each server’s image, the sites still on an older PHP and why, and what the release fixes. A site whose move failed has Try again there. The advance notice opens php.net’s announcement.

The details of PHP 8.4: each server has 8.4.26, one site's move failed and offers Try again, and what the release fixed

A security release also says what it fixes, such as 2 critical and 1 high. A site on an older release than the newest of its branch has its PHP in amber in the site lists, on its Overview tab and on its server’s page.

The alert address gets an email when php.net announces a security release, when one is out for a PHP version your sites run, and when its sites have moved or some could not. These emails are always sent. The address is set in Settings, then Monitoring.

The PHP releases schedule reads php.net every 15 minutes: its newest releases, its release candidates and its news. What a security release fixed comes from GitHub’s advisories for PHP.

A server’s new image comes from one of two places:

  • An install that pulls its images follows the published images of its release. A GitHub workflow rebuilds them when Docker’s official WordPress image has a newer PHP. That is usually a few hours after php.net. On Mondays it rebuilds every image, and publishes those whose packages changed. A rebuild is published only if it serves a PHP page.
  • An install that builds its own builds a new image on the server. It does so when php.net has a newer release and Docker’s base image has changed, and on Mondays from 03:00 UTC. A build that changed no package is thrown away.

Either way, each server gets a Refresh site images job, which runs beside its other jobs. Then each site on an older image gets a Recreate site container job, with its own rollback. The site does not answer for a second or two. Its files, its database and WordPress stay as they are.

To stop all of it, pause PHP releases on Automations → Schedules.

  • Docker’s WordPress image follows a PHP release by a few hours. Sites cannot move before it.
  • Only the images of the newest release and of the newest edge build are rebuilt. An install on an older one gets a new PHP with a WPL7 update, and the card says so.
  • A site busy with another job moves at the next hourly check.
  • A coming release’s fixes are not known before php.net publishes it.
  • php.net’s notice is read from its wording. A notice whose date does not read shows without one.
  • Sites hosted elsewhere are not updated. Their PHP is their host’s.