atom requirements

[juliangruber]

• if the user is on a specific release channel, like beta, they want to stay there. This is in contrast to other use cases, where if you're on 1.0.0-beta you're expected to upgrade to 1.0.0 next
• there's multiple zip files in a release, one for the app and one for symbols. We need to make it configurable which to use
• turn on prereleases

[daviwil]

Regarding the zip files one, this is for the macOS release asset. Atom delivers both atom-mac.zip and atom-mac-symbols.zip, so if the latter shows up first in the asset list it gets picked. We need a way to say "for macOS, use atom-mac.zip"

We also need a way to turn on the use of releases marked as prerelease. Atom marks beta releases as prerelease: https://github.com/atom/atom/releases/tag/v1.28.0-beta3

[daviwil]

One other thing I realized we need: x86 and x64 downloads for Windows releases as Atom currently provides both. Not sure if this should be a part of the URI structure or expressed another way. The trick is that Atom changes file naming conventions for the .exe, .nupkg, and RELEASES files to have -x64 in the 64-bit releases:

https://github.com/atom/atom/releases/tag/v1.28.0-beta3

[AuHau]

This would be an awesome addition that we are looking for. Is there a plan for implementing this?

[sonictl]

Regarding the zip files one, this is for the macOS release asset. Atom delivers both atom-mac.zip and atom-mac-symbols.zip, so if the latter shows up first in the asset list it gets picked. We need a way to say "for macOS, use atom-mac.zip"

We also need a way to turn on the use of releases marked as prerelease. Atom marks beta releases as prerelease: https://github.com/atom/atom/releases/tag/v1.28.0-beta3

what does the atom-mac-symbols.zip use for? How to use it? Thank you!!