[QUESTION] How to remove previous release files? about nucleus HOT 5 CLOSED

In order to be deterministic we don't allow actually deleting the old release, what you should do is

1. Have logic in your app to check if the current version is "dead" (by hitting the versions.json file) and if it is doing nothing other than checking for an update and showing some UI explaining this to the user
2. Release a newer version straight away, even if this is just the last known good version with the version number bumped in the package.json

from nucleus.

Hm, actually thinking about this, maybe we should make it so if the latest version is marked as dead all the metadata files are updated to not include those versions 🤔

Thoughts @Stoyvo ?

from nucleus.

Hey @MarshallOfSound

I was thinking maybe something along the lines of:

If release is marked dead, provide option to archive files elsewhere (non-public location) or remove files in that release.

I would hope many app developers have their own archive of their releases, but Nucleus could partially provide that (with moving dead files to archive). I personally do not need the previous releases made available based on my CI cycle.

from nucleus.

If release is marked dead, provide option to archive files elsewhere (non-public location) or remove files in that release.

This will make the update server non-deterministic. I.e. Files that once existed will not exist any more and this is a bad idea (especially for something as critical as an update server)

from nucleus.

As part of the work in #35 my suggestion above will be implemented.

maybe we should make it so if the latest version is marked as dead all the metadata files are updated to not include those versions

No dead version will appear in any win32 / darwin release metadata. How dead versions work for linux I'm not yet sure 🤔

from nucleus.