For a variety of reasons, Meld hasn’t had any non-source releases for a long time, so I only just discovered that after the release service changes (wonderful, no complaints) master.gnome.org was decommissioned. I couldn’t find any guidelines on how to distribute binaries now that the previous method isn’t available. How do other projects handle this, or is binary distribution just not supported now?
In general we ship pre-built things through flathub, or are you thinking of something like Windows MSIs?
GitLab lets you publish packages. I’m not 100% sure how to tie them to releases, but I think you list the URLs for the packages as part of the release’s assets.
You can attach build artefacts to a release page on GitLab.
Yes, this is specifically for Windows and macOS installers.
Yes, that’s what I tried, but it’s just a URL reference and linking to a pipeline artifact felt a bit unsatisfactory.
Thank you, this ended up being closest to what I was looking for. Because I couldn’t upload packages from the UI I assumed I didn’t have permissions, but just posting the CI results to the endpoint worked great. Cheers!
No, I meant you can literally upload a binary file when writing the markdown of the release. Download the result or the pipeline locally, edit the release message, press the paperclip and upload the file.
You can also use the GitLab command line utility from within the CI pipeline: look at how the release service CI template works for projects that are not under the GNOME group
1 Like
That didn’t occur to me, but you’re absolutely right that that would work, thanks!
That’s what I’m hoping to do for future releases, I just needed an interim manual option to make the most recent release available for Windows users.