wppaste
WordPress

find_core_auto_update(): object|false

Since
3.7.0
Source
wp-admin/includes/update.php:93
Gets the best available (and enabled) Auto-Update for WordPress core.

Description

If there's 1.2.3 and 1.3 on offer, it'll choose 1.3 if the installation allows it, else, 1.2.3.

Compatibility

WordPress
since 3.7.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Return value

object|false
The core update offering on success, false on failure.

Performance profile

How much work a call to find_core_auto_update() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Heavy

Reads stored settings via get_site_option(), cached per request but not free on a cold cache.

Scaling
Scales with input

The body loops, so the work grows with how much data it finds.

Instructions
6–19

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 41.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

  • transienttransientget_site_transient()called directly
  • hookthird-party callbacksapply_filters()one call below find_core_auto_update()
  • cacheobject cachewp_cache_get()one call below find_core_auto_update()
  • optionnetwork optionget_site_option()one call below find_core_auto_update()

Further down the call graph this can also reach serialize and query. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost find_core_auto_update() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always6–19get_site_transient()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 41 instructions, 6–19 executed per call, 8 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 2

Used by · 1

Source code

function find_core_auto_update() {	$updates = get_site_transient( 'update_core' ); 	if ( ! $updates || empty( $updates->updates ) ) {		return false;	} 	require_once ABSPATH . 'wp-admin/includes/class-wp-upgrader.php'; 	$auto_update = false;	$upgrader    = new WP_Automatic_Updater(); 	foreach ( $updates->updates as $update ) {		if ( 'autoupdate' !== $update->response ) {			continue;		} 		if ( ! $upgrader->should_update( 'core', $update, ABSPATH ) ) {			continue;		} 		if ( ! $auto_update || version_compare( $update->current, $auto_update->current, '>' ) ) {			$auto_update = $update;		}	} 	return $auto_update;}

Changelog

Introduced in 3.7.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 6.9.7 tag, from src/wp-admin/includes/update.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.