WordPress 6.0 update deploy failed

PHP-FPM has site-specific log files and global ones. Maybe the error somehow ended up there.

When this isn’t a Sage theme, then maybe that theme still somehow catches the PHP error and logs it somewhere else. So despite the 255 exit of WP CLI for those subsequent releases the site loads fine in frontend backend?

Alas. At this point, I have destroyed the problematic droplet(s), but thanks to you, I go forward with awareness of /var/log/php8.0-fpm.log, /var/log/auth.log and echo $?, among other things.

Roots University continues to succeed. :woman_student: