Windows installer md5 hash incorrect (multiple releases)

[justusbunsi]

Hi, the referenced md5 checksum for windows installer on tags v4.4.5 and v4.5.0 does not match the currently downloadable installer.

v4.4.5

Reference in release: a03806b7302767d0470d65d3f103fabb (which matches the one from v4.4.4)
Actual checksum (as of 2023-08-09): 396833b72a865be4b693f18ee2e34cde

v4.5.0

Reference in release: a03806b7302767d0470d65d3f103fabb (still which matches the one from v4.4.4)
Actual checksum (as of 2023-08-16): fd53c0afc26394ef5ce6a0922186de29

As it seem to be a reoccurring issue, is there anything missing in the release workflow? (see #928)

[davidcr01]

Hello.

Two PRs have been created to fix this problem:

• Fixed MD5 checksum for 4.5.0 #995
• Fixed MD5 checksum for 4.4.5 #994

This mistake is done because is necessary to check the MD5 checksums after the packages are generated, and then, change them before releasing the definitive tag.

Hope it helps.
Regards, David.

[justusbunsi]

Thanks for fixing the releases. I can confirm that it now works.

@davidcr01 anything I can help with, so that the mistake doesn't happen in the future again?

[davidcr01]

Thanks, but no further help from you is needed. If your problem is fixed, I assume I can close this issue for now.