This will upload an AppImage if a new release is created (from the release tab on github), with a v prefix (e.g. v1.0.0).
I am aware, this conflicts with the current approach which seems to be creating a tag locally and creating a release from that. But since the tag is currently a moving target and the aim of this is a manually triggered release, this might be justified.
Whereas for nightly builds, it might be interesting to https://nightly.link/ instead and avoid the moving tag as currently done.
This also deduplicates code by using a build matrix.
I am completely open to change the approach if you prefer otherwise. My main interest is getting a stable link to an immutable release.
References https://github.com/linuxdeploy/linuxdeploy-plugin-appimage/issues/21
This will upload an AppImage if a new release is created (from the release tab on github), with a
v
prefix (e.g.v1.0.0
).I am aware, this conflicts with the current approach which seems to be creating a tag locally and creating a release from that. But since the tag is currently a moving target and the aim of this is a manually triggered release, this might be justified.
Whereas for nightly builds, it might be interesting to https://nightly.link/ instead and avoid the moving tag as currently done.
This also deduplicates code by using a build matrix.
I am completely open to change the approach if you prefer otherwise. My main interest is getting a stable link to an immutable release.