This adds a new Github workflow which is only triggered after pushing new tags.
So we could easily create a Windows release installer by just pushing a new tag and no manual release build is required any more. The release process will get a bit simpler and less dependent on single persons.
I gave the resulting installer a quick testing using Wine and it looked quite good, except for random and non-reproducable crashes but this is due to the Wine setup.
To easily test this workflow I created a temporary repository and the resulting installer can be found there: https://github.com/eht16/geany-tmp/actions/runs/13227699835
@b4n @techee @giuspen what do you think?
If we want to go this road, I would prepare a corresponding change for G-P as well. You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4238
-- Commit Summary --
* Add Github action workflow to create Windows installer for releases
-- File Changes --
A .github/workflows/release-windows.yml (91)
-- Patch Links --
https://github.com/geany/geany/pull/4238.patch https://github.com/geany/geany/pull/4238.diff
Currently, the new workflow is more or less a copy of the existing Windows build workflow. We could discuss if we merge them into one and add some `if` to differentiate between normal and release builds or keep it as it is.
Without testing it or looking at any of it, it sounds like a wonderful idea, especially given humans resources availability, and even more for the Windows side of things.
I didn't look at anything (sorry), but do we have installers for the regular builds? If not, it might be interesting to have them so it's easier for users to test changes. Unless it's unreasonably costly or so.
I didn't look at anything (sorry), but do we have installers for the regular builds? If not, it might be interesting to have them so it's easier for users to test changes. Unless it's unreasonably costly or so.
Actually we do have them already, for master and PR builds.
I don't think this makes #4223 obsolete because it is probably always good to be able to create release installers manually, either for testing or as backup in case the Github actions suddenly disappear or whatever.
Hallo Enrico, sorry I haven't followed up yet on your latest comments, I have been busy with a release of my own main open source project. I'll catch up in the next few days! As you say that we already have automatically built installers for every commit on the master or PRs, what difference has this action, that happens only on tags, compared to that? Certainly I would recommend preparing automated builds also for the G-P as in fact I believe the current plugins are broken for a missing included header on mingw64.
@b4n @techee @giuspen what do you think?
I think it would be great!
github-comments@lists.geany.org