Consider pointing to releases page on Linux instead of tarball #1

New Issue

giteasync · 2025-09-10T23:56:33-05:00

giteasync commented

2025-09-10 23:56:33 -05:00

Originally created by @jackmawer on GitHub.

While linking directly to a tarball is useful for users that use a directly extracted copy of VSCodium, for AppImage users being redirected to an archive when expecting a new AppImage is a confusing and frustrating experience.

Additionally, for users who use either Flatpak or their distribution's package manager, the experience is equally as confusing - potentially on these platforms could the update check either be disabled or the link replaced with a hint to update via their package manager?

Both of these potential issues could be resolved by linking directly to the Releases page, as every option of distribution is readily available, and the release notes could contain a reminder of how to update via a package manager.

I hope the reasoning behind this proposal makes sense, and I am eager to hear your opinions.

Originally created by @jackmawer on GitHub. While linking directly to a tarball is useful for users that use a directly extracted copy of VSCodium, for AppImage users being redirected to an archive when expecting a new AppImage is a confusing and frustrating experience. Additionally, for users who use either Flatpak or their distribution's package manager, the experience is equally as confusing - potentially on these platforms could the update check either be disabled or the link replaced with a hint to update via their package manager? Both of these potential issues could be resolved by linking directly to the [Releases page](https://github.com/VSCodium/vscodium/releases/), as every option of distribution is readily available, and the release notes could contain a reminder of how to update via a package manager. I hope the reasoning behind this proposal makes sense, and I am eager to hear your opinions.

giteasync commented

2025-09-10 23:56:33 -05:00

@mattmess1221 commented on GitHub:

I would rather there be options based on the platform path, which is how Microsoft's update server handles it.

i.e. linux/x64/deb for the debian package or linux/x64/archive for the universal archive.

Microsoft's version api has a path like this where platform is something like win32-x64-user or linux-arm64-archive

https://update.code.visualstudio.com/api/versions/commit:{COMMIT}/{platform}/{quality}

Though afaik, the vscode linux client update handler just checks for updates and doesn't bother downloading anything. It always just links to the download page.

@mattmess1221 commented on GitHub: I would rather there be options based on the platform path, which is how Microsoft's update server handles it. i.e. `linux/x64/deb` for the debian package or `linux/x64/archive` for the universal archive. Microsoft's version api has a path like this where platform is something like `win32-x64-user` or `linux-arm64-archive` `https://update.code.visualstudio.com/api/versions/commit:{COMMIT}/{platform}/{quality}` Though afaik, the vscode linux client update handler just checks for updates and doesn't bother downloading anything. It always just links to the download page.

giteasync referenced this issue

2025-09-10 23:56:36 -05:00

[PR #1] [MERGED] Add integrity checker #8

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: VSCodium/versions#1