The build number (the last four digits) is higher on the earlier release. This happens every once in a while with both server and clients, but it’s rare and sometimes in error (like today, it would seem). It usually indicates different branches being worked on simultaneously. Nothing wrong with that, but a public (beta or stable) release should always have a higher build number than the previous one.
I updated manually, but like I said, that release got pulled for unknown reasons. Probably because it was a build from a different branch and therefore not meant for release (yet).
