devtrackers.gg
So we think that there was a cache issue with a version of the Linux server, and a few people downloaded an old cached version instead of the latest correct version when updating last night.
So the solution is for the server host to download a fresh copy of the linux headless server
If build 46132 was released as version 0.17.56, then releasing 46133 should be done as 0.17.57. I wouldn't ever expect to see two releases with the same version but with different build numbers.
The deployment of 46132 crashed midway through, and since the deploy was not completed, there was no reason to bump the version number.
The problem was that it failed after it had already uploaded the Linux headless, so when the next deploy succeeded, the old failed deploy was still in the cache