Create CI Releases

[BakasuraRCE]

Hi,

I created this workflow to build Linux binaries for every commit made on the master branch.

It does not include the par2 binary, the idea is to extend the functionality to generate binaries of all operating systems in the following pull requests.

Could you validate if the resulting binary meets the packaging characteristics?

[mbruel]

I don't want to build binaries for every commit...
Only on new Tags. (new versions)

[mbruel]

other than that, I'm going to switch to Qt v5.15.0 except maybe for Windows.
I've just tried it on MacOS and I'm getting lots of deprecated to fix... It will be the last v5 before the v6. That's the transition version.
The AppImage should include par2 and/or a compiled version of parpar in the future ;)

[mbruel]

Thanks I'll have a look at it but I'm more interested for auto build for Windows and MacOS.
For Linux it's too complicated. I've sorted it out yesterday.
To make it short: linuxdeployqt needs debian 11 (for libc) which only supports ssl 1.1 and doesn't have Qt6.
So from the next release, I'll build manually (script) 2 versions on my Debian 11 server:

• ngPost_v4.16_libssl1.1-x86_64.AppImage (based on Qt 6.2 LTS with libssl 1.1)
• ngPost_v4.16_libssl3-x86_64.AppImage (based on Qt6.5 LTS with libssl 3)