Fix: auto update check error should not fail the running command

[Copilot]

When the background update check hits a network/HTTP error (e.g. 401, 403 rate-limit), CLI_Command::get_updates() calls WP_CLI::error(), which exits the process — silently killing whatever command the user actually ran.

Changes

• Runner::auto_check_update(): Replace the bare ob_start() / WP_CLI::run_command() pattern with WP_CLI::runcommand() using exit_error => false and return => 'all'
  • exit_error => false sets $capture_exit = true so WP_CLI::error() throws ExitException instead of calling exit()
  • return => 'all' swaps in an Execution logger that captures stdout/stderr in memory — the error message is never printed to the terminal
  • On failure, a WP_CLI::debug() message is emitted (visible with --debug) and the check silently returns without affecting the user's command

// Before: any HTTP error in get_updates() would call exit(1)
ob_start();
WP_CLI::run_command( [ 'cli', 'check-update' ], [ 'format' => 'count' ] );
$count = ob_get_clean();

// After: errors are captured, not propagated
$result = WP_CLI::runcommand(
    'cli check-update --format=count',
    [ 'launch' => false, 'exit_error' => false, 'return' => 'all' ]
);
if ( ! is_object( $result ) || $result->return_code ) {
    WP_CLI::debug( 'Background update check failed: ' . ( is_object( $result ) ? trim( $result->stderr ) : '' ), 'auto-update' );
    return;
}

Summary by CodeRabbit

• Bug Fixes
  • Improved update-availability checking to tolerate network/HTTP failures without interrupting normal command execution.
  • Added more informative diagnostics when the update check fails.
  • Enhanced reliability in determining whether updates are available and reporting the correct update count.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
php/WP_CLI/Runner.php	0.00%	9 Missing ⚠️

📢 Thoughts on this report? Let us know!