Download Latest WordPress, Not Last One Found.

[dcole07]

This is an edge case scenario that likely doesn't effect much of anyone, but if someone is running WordPress 2.8.2 and decides to upgrade right after WordPress 2.8.4 has been released, then they will upgrade to WordPress 2.8.3. This problem arises because WordPress doesn't check for new versions every second, so there is a small window of time were the newest version of WordPress your being told about isn't actually the most current version.

To fix this problem, I suggest WordPress upgrade to latest.zip, instead of the version number, e.g. wordpress-2.8.4.zip.

[Denis-de-Bernardy]

This would actually depend on the wp.org API

[dd32]

Putting it in the wp.org API is a semi-good idea, But i think returning the static files is better than a file which will change from release to release.

I'd suggest just clearing the cache and forcing a new API request when the upgrade page is visited..

It'll have the benefit that people can even just visit their upgrade page and upgrade even if WordPress hasn't realised theres a new release available.

[matt]

I agree with DD32, this is really more an issue that we shouldn't use the cached value when visiting the upgrade page manually, or at least have a re-check button.

[ryan]

We run wp_version_check() in update-core.php before showing anything. This forces a recheck every time update-core.php is loaded.

[ryan]

See [10583] #9108