Hypernode Deploy 4.10.0: PHP 8.5 Support and support for Tideways & Rumvision Annotations

We’re pleased to announce that Hypernode Deploy 4.10.0, together with hypernode/deploy-configuration 3.9.0, adds support for PHP 8.5 images and two new after-deploy tasks for Rumvision and Tideways. This release also includes several reliability fixes for brancher environments and the deploy command flow.

PHP 8.5

You can now build and deploy with PHP 8.5 images. For PHP 8.5 we use MySQL 8.4 for the deploy images, matching the first PHP 8.5-compatible Magento release.

To use PHP 8.5, set it in your deploy.php:

$configuration->setPhpVersion('8.5');

New AfterDeploy Tasks: Rumvision and Tideways

Hypernode Deploy now ships after-deploy tasks for Rumvision and Tideways. You can add them to your deploy.php to have your caches updated automatically after each successful deploy.

For Tideways:

$configuration->addAfterDeployTask(
    new \Hypernode\DeployConfiguration\AfterDeployTask\Tideways(
        apiKey: 'tw_A0...', // or through an env variable with env(...)
        description: 'test'
    )
);

For Rumvision:

$configuration->addAfterDeployTask(
    new \Hypernode\DeployConfiguration\AfterDeployTask\Rumvision(
        apiKey: 'xomyahbs.vA...', // or through an env variable with env(...)
        domains: ['example.com']
    )
);

In both cases you can pass the API key directly or reference it through an environment variable with env(...), so you don’t have to commit the key to your repository.

Bug Fixes and Improvements

  • Brancher deploys no longer fail when the Hypernode API returns a transient server error during logbook polling.
  • In the commands flow, Hypernode Deploy now only executes after-deploy tasks that are actual commands, preventing non-command tasks from running twice in the wrong context.
  • Node.js 26 is now supported in the deploy images.

How to Update

Simply use the new hypernode/deploy 4.10.0 docker image (or use simply the latest tags). It already includes hypernode/deploy-configuration 3.9.0, so no changes to your composer.json are needed.

  • Hypernode Deploy: https://github.com/ByteInternet/hypernode-deploy/releases/tag/4.10.0
  • Hypernode Deploy Configuration: https://github.com/ByteInternet/hypernode-deploy-configuration/releases/tag/3.9.0

Let us know if you run into any issues or have questions via our support channels.