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_versionnow accepts2.10and2.11as values, both through the control panel and the API.- The
composer210binary ships Composer2.10.3, andcomposer211ships Composer2.11.1. - The
composer2alias has been updated to Composer2.11.1as well, so2.xusers stay on the latest 2 release. - WP-CLI (
wp) has been updated from2.6.0to2.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.