Preparing for v0.14.2 release

[stoffu]

No description provided.

[stoffu]

I see some very strange behavior of GitHub Actions CI: for the Ubuntu build, the CI generates two different versions of aeon-wallet-gui at random, one broken and the other properly working, over multiple re-runs. The likelihood of generating the broken binary is much higher (~80%).

I noticed that the broken binary is a bit larger (16531416 bytes) than the proper one (16510936 bytes). See some sample results:

• (broken) https://github.com/stoffu/monero-core/runs/5377071475?check_suite_focus=true
• (proper) https://github.com/stoffu/monero-core/runs/5385232077?check_suite_focus=true

I couldn't reproduce this behavior on my local virtual machine running Ubuntu 18.04. I really don't know how this is caused and how to fix it. Though it feels weird and annoying, the way of producing release binaries would be to just re-run the CI multiple times until it generates the proper binary.

[BigslimVdub]

Any way to get the artifacts signed? MacOS is giving the unknown developer error.

[stoffu]

@BigslimVdub
You can control+click the app icon and click on "Open" to get around this warning.

I'm not familiar with this app signing business, but I doubt it would be feasible for our case where we build the app on the GitHub CI and most of the developers want to stay anonymous.