Repository navigation
Require wp-cli/wp-cli ^3.0 to fix SQLite Behat failures - #46
Conversation
With wp-cli/wp-cli 3.0 not yet tagged as stable and prefer-stable enabled, Composer resolved wp-cli/wp-cli v2.12.0, which in turn capped wp-cli/wp-cli-tests at v5.0.11 (newer releases require wp-cli ^2.13/^3.0). That old test framework no longer works with the current SQLite integration plugin, making every Behat run on SQLite fail in "Given a WP install". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UWTd5mtWhh1gEboQejY1nD
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Align with the other WP-CLI packages. Allowing ^2 let prefer-stable pick wp-cli/wp-cli v2.12.0, which capped wp-cli-tests at v5.0.11. Requiring ^3.0 resolves to 3.0.x-dev and lets wp-cli-tests ^5 resolve to the latest release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UWTd5mtWhh1gEboQejY1nD
Behat tests on SQLite fail in
Given a WP installwith:Cause
This package required
wp-cli/wp-cli: ^2 || ^3.wp-cli/wp-cli3.0 hasn't been tagged as stable yet, so withprefer-stableComposer pickedv2.12.0. Everywp-cli/wp-cli-testsrelease from v5.1.0 on needswp-cli/wp-cli^2.13or^3.0, so Composer quietly fell back to wp-cli-tests v5.0.11, which no longer works with the current SQLite integration plugin.The other WP-CLI packages already require
wp-cli/wp-cli: ^3.0. Only3.0.x-devsatisfies that, so their test dependencies resolve to the latest releases.Fix
Require
wp-cli/wp-cli: ^3.0to match the other packages. Composer now resolveswp-cli/wp-cli3.0.x-dev, wp-cli-tests v5.5.3, entity-command v3 and extension-command v3. I confirmed this locally withcomposer update --dry-run.🤖 Generated with Claude Code
https://claude.ai/code/session_01UWTd5mtWhh1gEboQejY1nD