Updating WordPress outside of wp-cli

[ataylorme]

I was wondering if the update verification can be run stand-alone, after updating WordPress outside of wp-cli. Specifically, after updating with Composer.

[danielbachhuber]

Interesting thought. There would be a couple nuances to such an implementation:

1. This update verification code is dependent on a working WordPress install because it makes a HTTP request against the site. composer update doesn't necessarily happen within the context of a working WordPress install.
2. We'd need to adapt much of the code to work as a Composer plugin. To be honest, the code itself is quite minimal. I'm not sure there'd be much overlap between the two implementations.

[ataylorme]

I was thinking more of someone uses Composer and a CI process to update WordPress being able to run a wp-cli command on a staging environment, or wherever the working WordPress installation lives, to verify the update didn't break anything.

[danielbachhuber]

I was thinking more of someone uses Composer and a CI process to update WordPress being able to run a wp-cli command on a staging environment, or wherever the working WordPress installation lives, to verify the update didn't break anything.

Ah, this would be easier to do. We could expose some command that performs the basic heuristic check before and after.