vscode/releases page missing binaries

[citrusui]

Just wondering... why doesn't the releases page have vscode binaries? I only see the source code downloads. Atom and Brackets both use GitHub to publish binaries...

Would be handy in case someone wanted to download an older release or if Microsoft's servers were down.

Inspired by #1084

[hashhar]

This is a good idea. Would make it much easier for me for to use my download utility.

[egamma]

@chrisdias fyi.

We need to distinguish between vscode and Visual Studio Code see here for an explanation.
Currently we do not make milestone builds available for vscode. Something we can consider.

[hoovercj]

Is this sufficient to close the issue? https://github.com/Microsoft/vscode/wiki/Previous-Releases

[citrusui]

It's just odd how there's no exe or zips on the Releases page... pretty easy to do, just add a changelog and tag, then upload the files.

[hashhar]

@hoovercj It's good enough I guess. It's also machine parseable.

[chelming]

@hoovercj no, that's not sufficient (nor does it exist any more). I'd specifically like to be able to use the releases api to check for and download latest releases. Currently it returns nothing: https://api.github.com/repos/Microsoft/vscode/releases

[redtux]

Hi everybody, I just had a look for binary releases of VS Code ("OSS") in this git repository. While I found tarballs of the source at https://github.com/microsoft/vscode/releases there are no .deb, .rpm, .exe, or .dmg files like in other similar projects. What would be necessary for this to happen? How can we help?

JFYI: I have already read all related issues (also concerning licensing, the marketplace, etc.), but found no answer to my question. The only thing I found was this issue from December 2015.

A good example for what this could look like is GitHub's Atom (now also part of the Microsoft family). Build scripts can be found at VS Codium (that I do not belong to). CI building can be done automagically (e.g. with every new tag) using GitHub Actions (like Jenkins, GitLab CI, Travis).

• https://github.com/atom/atom/releases
• https://atom.io/releases
• https://github.com/VSCodium/vscodium
• https://github.com/actions/create-release

[Hydroidev]

While a direct yes or no answer on this topic from someone more involved in the repository would be nice, I can see why it hasn't been a priority. Both the Microsoft branded binaries and the binaries built directly from this repo are already easily accessible, the latter of which is supplied on the VSCodium project earlier mentioned.

I definitely agree that having these binaries available directly in this repository would be more organized and convenient than relying on another repository. As it stands, the binaries produced by the VSCodium project are almost no different than would be made by CI. Either way, after 4 years this issue should be given a definitive answer; is this being worked on? or should it be closed?