I just noticed that the latest Windows executables for 1.18.5 have NOT been signed. Since I think this is the first time I’ve ever seen this, I thought I’d check to make certain this was intentional. Is this how things will be going forward?
No, it was a mistake and should be fixed for future releases. See:
I’m getting a new code signing certificate, this time for the Foundation and not some randomly involved company… However it’ll take a few days to get “verified” and whatnot.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.