Question: About Github Releases

clowd / Clowd.Squirrel

Quick and easy installer and automatic updates for cross-platform dotnet applications

426 stars 39 forks source link

Question: About Github Releases #143

Closed mike-hanson closed 1 year ago

mike-hanson commented 1 year ago

May seem like a stupid question, but the documentation is not 100% clear to me.

When I create an update release in Github do I need to include all previous NuGet packages or just the latest full and delta packages along with the setup executable and the RELEASES file.

Thanks in advance of response.

caesay commented 1 year ago

Your GitHub release assets should contain:

Latest full package
Latest delta package
RELEASES file containing lines only for these two packages
Setup.exe / Setup.pkg

If you are using v3, there is an automated deployment command which can create a draft GitHub release and upload everything for you in the proper configuration.

Mageofdavodo commented 1 year ago

@caesay Sorry for bringing this up again.

But I'm unsure as to how you manage to keep the RELEASES clean with only these two packages.

I'm trying to have a release flow exactly like this but in order to generate a delta package it needs to have more than these two lines in the RELEASES file. It needs a reference to the previous full/delta.

I plan on using the github-down to download the previous artifacts but would end up having the same issue as OP.

Im on version 2.9.42 btw.