Publish new release binaries once infrastructure is updated

[psifertex]

Checklist

• I have searched the issue tracker for open issues that relate to the same problem, before opening a new one.
• This issue only relates to a single bug. I will open new issues for any other problems.

Description

I know I've downloaded windows releases before but the build is missing for 3.7.0. Is this intentional?

Steps to Reproduce

1. Visit https://github.com/Jacalz/rymdport/releases/tag/v3.7.0
2. Notice windows is missing.

Screenshots

No response

Rymdport version

3.7.0

Operating System

Other (specify below)

Operating System Version

N/A, download is unavailable no matter the browser platform

Go Compiler Version

No response

Additional Information

No response

[Jacalz]

It is all there in the release notes:

"NOTE: Due to problems with updated Go compiler images in https://github.com/fyne-io/fyne-cross-images, this release is missing release builds for many platforms and architectures. I recommend installing from Flathub or your package manager where available."

Basically, I increased the minimum Go compiler that could be used to build this project and it turned out that the cross-compile infrastructure hadn't been updated.

However, as it happens, the updated docker images were released just two days ago. I am just waiting for them to become available on https://fynelabs.com/geoffrey/ and then I will update the release (or do a new one potentially).

[Jacalz]

I am sorry for the problems this might have caused. One might argue that I should have not published the release (or rather taken it down) but I figured no release or one with lack of binaries would be about as problematic for affected users/platforms. The distribution packages on Linux are still working out well :)

[psifertex]

Sorry for missing that -- one thing that might have been helpful is explicitly putting "windows" in the text stating that builds are intentionally missing. I did a search on the releases page and was surprised to see windows wasn't anywhere on it. It didn't help that the previous release binaries were collapsed so none of those showed up either. I did eventually find the older release binaries and use those.

[Jacalz]

No worries. Sorry for the confusion and infrastructure problems. It isn't easy to manage the time and money constraints of open source projects, especially not when juggling multiple ones at the same time 😅 I do however promise to publish binaries as soon as possible but I don't have any timeframe. The plan is to do a v3.7.1 release with some bug fixes in a few weeks 👍

[psifertex]

No rush! Your tool is super useful and I appreciate it. You get what you pay for and in this case I mostly just filed the issue to see whether the documentation needed updating more than trying to make extra work on the build sign. :- )

As I said, my specific issue was solved as soon as I realized I could grab the older release, it works well enough for my purposes, was just harder to find than expected.

[Jacalz]

Thanks. I appreciate the kind words. Feel free to report any other issues or ideas you have :)