The MD5 checksums for the setups I downloaded today are:
setup_fallout.exe 70F3984F240841A0DB216274D35AC734
setup_fallout_2.exe EC694BDB4DD68468989A4075A9B1E1D2

http://www.gog.com/en/forum/operation_flashpoint_series/cd_key/perm=7/#p_b_7
Seems that all new downloads will have different md5's now.

Yeah I figured they just needed to update them. It would seem to me that it would be easier to have the md5 hash parsed at the downloads page for the game automatically whenever a new build is posted - instead of manual updates in forum.

Er, the post implies that the MD5 posts aren't needed anymore for new versions of the installer. The installer itself will verify the MD5 of the archive when you run it. Why bother with recording the MD5s then?

Posting the md5 hash is still a good paradigm to follow even if the installer has the ability to do so on it's contents. Not only is it open source easy to automate software, but also greatly aids in troubleshooting (especially for the bandwidth challenged customers). Quite honestly if someone were having install problems the 1st logical step in troubleshooting would be to verify the hash. This would easily identify an improper bit order that could possibly affect the installer's ability to properly report to the user the difference in hash.
Plus you can easily check if your build of a game is current with GOG, especially in these early stages where the kinks are being worked out and new builds are frequent.
Saves time troubleshooting if needed - saves money on bandwidth. Posting the current md5 hashes I feel is still very relevant.