WP ENV installs latest xdebug without option to control the extension version

[udidol]

This ticket is about WP ENV.
xDebug just released (Dec 8th 2022) v3.2.0.
In v3.2.0, xDebug drops support of PHP <=7.4.

wp-env, as part of its installation process, installs the latest xdebug (pecl install xdebug).

This breaks the wp-env build process on machines running PHP <=7.4.

Please add an option via the wp-env.json to control PHP Extension versions.

[johnbillion]

Thanks for the report @udidol !

[desrosj]

I'm not sure this is something we can fix here.

One clarification, the wp-env package is ​maintained over in the Gutenberg repository. The Docker setup for local WordPress development is found and maintained within this SVN repository.

The main difference, by default, is that wp-env uses the ​"official" (really unofficial) images that are maintained by the Docker team instead of the ​images that the WordPress team maintains. These are updated in the ​corresponding GitHub repository. However, it seems that they ​no longer release PHP 7.4 updates and only update images for the most recent version of WP.

I did look within wp-env, though, and it seems that you're right in saying that package is managing xDebug within the container, but there is a ​hard coded exception for PHP 7.x where only up to xdebug-3.1.6 is used. Using xDebug on PHP < 7.2 ​also explicitly returns an error.

It looks like this was ​suggested here and added in ​GB-50490, which roughly aligns with when this ticket was opened originally.

@udidol could you do some testing to see if that has been resolved for you? I was unable to reproduce with the latest version of wp-env.

Adding a suggestion to close as worksforme since I'm unable to reproduce.