Composer 2.10 and 2.11 are now supported on Hypernode. You can select either version as the default composer binary on your Hypernode, alongside the existing 2.2 through 2.9 options.

What’s New

  • composer_version now accepts 2.10 and 2.11 as values, both through the control panel and the API.
  • The composer210 binary ships Composer 2.10.3, and composer211 ships Composer 2.11.1.
  • The composer2 alias has been updated to Composer 2.11.1 as well, so 2.x users stay on the latest 2 release.
  • WP-CLI (wp) has been updated from 2.6.0 to 2.12.0.

Selecting a new version symlinks /usr/local/bin/composer to the matching binary, so existing scripts and CI pipelines keep working without changes.

How to Switch

To set Composer 2.11 as the default on your node:

app@abcdef-example-magweb-cmbl:~$ hypernode-systemctl settings composer_version 2.11

Action Required

None. This is an opt-in change. If you don’t change the composer_version setting, your Hypernode keeps its current Composer version.

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