The article literally states that should you download the latest version from their site directly and then use the installer to update manually. Who knows if those who were effected already could have something else compromising the update/install process. I wouldnt update from the built in updater until the new fix with certificate and signature verification is released.
While I agree with you I did just want to point out one thing.
This:
it’s mathematically impossible to fake.
Is not entirely true persay, every hashing function does have collisions that can occur. But the likely hood that someone baked an exploit in that kept the application functioning while adding their backdoor all the while somehow creating a hash collision with the original fingerprint is practically zero and honestly if someone did pull that off, fucking hats off because that has to be some sort of math and coding wizard beyond most. I should also point out that the file size would most likely/have to be different so there should be other methods of detecting the compromised build regardless.
Sorry I know that was very pedantic of me but I did want to call that out because its technically possible but the actual likely hood has to be so miniscule its almost irrelevant along with the fact that other tells would surely exist.
I would just follow their advice, download the newest version from their site directly and use the new versions installer to update manually. I would probably do the same thing when the newest version with certificate and signature verification releases, after that I would assume you should be good to go. However its probably also worth scanning your system for malware just incase you updated during the time frame the attack was live.