Running `env:cli db` commands fails due to failed certificate validation

[desrosj]

#63876 solved an issue where the installation script for the local development environment was failing due to upstream changes to the base container for the PHP Docker images. That was ultimately solved by passing --defaults to the db WP-CLI commands in installs.js.

@westonruter discovered another scenario where this issue surfaces: any WP-CLI db commands called through npm run env:cli.

In r60735, a change was made to the installation-related code in the local development environment that invokes any wp db commands to circumvent a failure caused by the presence of a self-signed certificate within the certificate chain.

However, that did not fix any wp db commands called through the env:cli npm script. This aims to do that by adding --defaults anytime env:cli is run with a command nested under db.

Trac ticket: Core-64218.

[desrosj]

Noting that this should likely be backported to all versions with support for PHP 8.1 or higher, as those are the images that are or will be affected.

For me current in trunk export working fine.

$ npm run env:cli db export

> WordPress@6.9.0 env:cli
> node ./tools/local-env/scripts/docker.js exec --user wp_php cli wp db export

Success: Exported to 'wordpress_develop-2025-11-08-f56a684.sql'.

For me current in trunk export working fine.

@mukeshpanchal27 to confirm, you meant that it was working fine without this PR? If so, which PHP version were you using? This issue currently only affects the PHP >= 8.3 wordpressdevelop Docker images.

I'm going to commit this ahead of RC1, but it's a build tool-related change so it can be reverted or adjusted at any point of the release cycle.

[desrosj]

Fixed in [61196].

Merged in r61196.