Delete old release and create new release before uploading to it

[probonopd]

Currently, https://github.com/probonopd/static-tools/releases/tag/continuous shows eda9edf even though the files attached to it are from newer commits.

We need to

• Check whether the continuous release belongs to the same sha commit as what we are currently building
• If not, then we need to delete the old continuous release and create a new one before we start uploading to it
• The above should only be done once we know that the build succeeded up to the point where we want to upload

@Tachi107 do you know how to do this?

[Tachi107]

As the jobs run in parallel, I think that this could be hard to coordinate. Would it be simpler to tell the other tools to look for https://github.com/probonopd/static-tools/releases/latest instead of https://github.com/probonopd/static-tools/releases/tag/continuous?

[probonopd]

As the jobs run in parallel, I think that this could be hard to coordinate.

Why? If we delete the old and make a new release when the sha of the release doesn't match the sha of the currently running build, then only the first of the running builds will trigger the re-creation of the release. Because for the other builds, the sha will match.

[Tachi107]

What if two builds try to delete the release at the same time? Or what if one deletes the release and starts uploading the artifacts, and then another job deletes the newly created release because the API has returned cached results?

[probonopd]

Apparently this is the way how to do it:

https://github.com/AppImage/AppImageUpdate/blob/main/.github/workflows/main.yml

• Upload to GitHub Artifacts
• Then, download from GitHub Artifacts and create a new release and upload the artifacts there

it then looks like this:

[Tachi107]

NooDS uses this simple job: https://github.com/Hydr8gon/NooDS/blob/2e09bf6ab39e205c692229fe14f540774a8a94bd/.github/workflows/autobuild.yml#L131-L154