Skip to content

Add Xdebug to the PHP 8.6 image - #231

Open
desrosj wants to merge 1 commit into
trunkfrom
add/xdebug-php-8.6
Open

desrosj wants to merge 1 commit into
trunkfrom
add/xdebug-php-8.6

Conversation

@desrosj

@desrosj desrosj commented Nov 10, 2026

Copy link
Copy Markdown
Member

Follow-up to #230. This installs Xdebug on the PHP 8.6 image using PIE.

Changes

  • PHP 8.6: installs xdebug/xdebug:3.6.0alpha1 with pie install --skip-enable-extension. 3.6.0alpha1 is currently the only Xdebug release whose Packagist metadata declares PHP 8.6 support (>=8.2,<8.7); 3.5.3 is capped at <8.6. Because the exact version is given, PIE resolves the alpha without an @alpha stability flag.
  • The PIE image is bind-mounted for the RUN step only, the same way as on 8.1–8.5, so PIE is not shipped in the final image.
  • libtool is added to the 8.6 apt packages, matching 8.1–8.5 (PIE warns when libtoolize is missing).
  • As before, Xdebug is installed but not enabled; entrypoint/common.sh enables it when LOCAL_PHP_XDEBUG=true.

Generated by running php update.php; only images/8.6/php/Dockerfile changed.

Not changed

PCOV, Memcached, and Imagick are still not installed on 8.6, as their latest releases don't compile against it yet (see #230).

Testing

Built images/8.6/php locally:

  • docker run --rm -e LOCAL_PHP_XDEBUG=true <image> php -v reports PHP 8.6.0RC4 ... with Xdebug v3.6.0alpha1.
  • Without LOCAL_PHP_XDEBUG, Xdebug isn't loaded.

🤖 Generated with Claude Code

Installs Xdebug 3.6.0alpha1 through PIE. This is currently the only
Xdebug release that declares support for PHP 8.6 (>=8.2,<8.7).

Like the other images, Xdebug is installed but not enabled, and is
turned on at runtime with LOCAL_PHP_XDEBUG=true. libtool is also added,
matching the other PIE-based images.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@desrosj desrosj self-assigned this Nov 10, 2026
@desrosj
desrosj requested a review from a team November 10, 2026 19:43
@desrosj desrosj moved this from Backlog to In review in WordPress Project Build Tooling Nov 10, 2026
@desrosj

desrosj commented Nov 10, 2026

Copy link
Copy Markdown
Member Author

I've run the wordpress-develop unit tests using --group xdebug and it looks like there are no unexpected failures or issues.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

1 participant