Why wasn’t your pull request included in the lastest WP-CLI release?
Honestly, it’s because I haven’t had time to come back and address some PR feedback:
If anyone is good with working on Behat tests, I’d love the help, otherwise, I’m just juggling being pulling in different directions.
In terms of this specific request, I’ve added ticket in an upcoming sprint to upgrade wpcli.
2 Likes
Many thanks for your quick reply and the update!
No problem I know how it is. Keep up the good work.
Unfortunately I’m not the right person for this either.
Anyone else who can help and has some insight?
WP-CLI version 2.11.0 has been released but unfortunately without the fix to handle spaces within the path to the PHP binary so the included WP-CLI version in the Local app can’t be updated via the usual wp cli update command.
1 Like
I installed the new version of wp-cli.phar manually and it seems to work even though it breaks the code signing of the Local app.
1 Like
Another easier way to update the WP-CLI version is to open a site shell for a website that are using the included php version 8.1.29 in the Local app (to avoid the space in Application Support) and run the wp cli update command but it will still break the code signing of the Local app since a bundled resource has been modified.
export PATH="/Applications/Local.app/Contents/Resources/extraResources/lightning-services/php-8.1.29+0/bin/darwin/bin:$PATH"
Edit: I’m using the Apparency app to check the code signatures.
2 Likes