Plugin package is old version when upgrading plugin shortly after release

[joehoyle]

The past few times I have done plugin releases, I have noticed an issue with the wrong plugin package being downloaded.

For example, I release a new version of a plugin via SVN. The plugin update appears on .org, and the download link downloads the new version.

The update also appears in a WordPress install shortly after (assuming transients are deleted for the fastest way to get the update to show). If I then Upgrade the plugin from the, WordPress install the Upgrader Skin does the usual Downloading Plugin... and the package (zip) that is shown to be downloading is the previous version. Of course, it does download the previous version and again shows an update is available.

After about 5-10 minutes this usually fixes it's self.

I don't know how the .org side of things work, is it possible that the updated version will show up, but whatever is responsible for getting the latest package is relying on a different cache or something?

[willmot]

Spoke to Otto about this at WPCS, it's a known issue.

Best option is to simply delay your auto update script for 30 min or so.

[Otto42]

This should be mostly fixed now, because the plugin updater runs on a much faster cycle than before.

However it is still possible if you catch it within about 1-2 minutes. Not much we can do about that, each server updates on its own schedule. Give it 5 minutes.