Checking our historical releases, it turns out we've made this mistake many times. In fact we've almost never posted the checksum for the correct name!
Are checksums important in this day and age? They were very useful back in the days when a release announcement was a PGP-signed email, and a release tarball was something you'd grab from some local FTP mirror. But nowadays the most secure way to get our release announcements is an HTTPS web page from GitHub, and the normal way to get the tarball is an HTTPS download from GitHub. So there's not much of a difference in terms of security, so what advantage does the checksum have?
In terms of integrity, only insiders (people with write permission on the GitHub repository) can edit a release announcement, and this is unlikely to be detected in real time but has a public log. Changing the release itself (as in, moving the tag to a different commit) is also something only insiders can do, with a more restricted access list; it is unlikely to be detected in real time (but trivial to check), but I'm not sure how apparent it would be who and when the tampering happened. I don't see a clear advantage to the release announcement in terms of integrity. Unless a third party decides to guarantee the integrity of the release announcement somehow, but then they could also guarantee the integrity of the release content if they want — and in fact I'd expect them to actually archive the release, since that guarantees availability of the content in addition to non-tampering.
If we stop providing checksums, is that a real loss?