Ensure db commands work with env:cli

[desrosj]

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.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props desrosj, westonruter, mukesh27.

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

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[westonruter]

I tried adding LOCAL_PHP="8.4-fpm" to my .env (after having downgraded to 8.2-fpm due to this issue), and after a restart, I got the failure again on trunk:

$ npm run env:cli db export

> [email protected] env:cli
> node ./tools/local-env/scripts/docker.js exec --user wp_php cli wp db export

Warning: Failed to get current character set of the posts table. Reason: ERROR 2026 (HY000): TLS/SSL error: self-signed certificate in certificate chain

mariadb-dump: Got error: 2026: "TLS/SSL error: self-signed certificate in certificate chain" when trying to connect

Upon switching to this branch, the issue is fixed!

$ npm run env:cli db export

> [email protected] env:cli
> node ./tools/local-env/scripts/docker.js exec --user wp_php cli wp db export

Success: Exported to 'wordpress_develop-2025-11-07-bcb8816.sql'.

Thanks!

[mukeshpanchal27]

For me current in trunk export working fine.

$ npm run env:cli db export

> [email protected] 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'.