Update to `1.71.0`

[daiyam]

Hello,

In the process of trying to debrand (when doing the insider version), I've overlooked several issues:

On macOS

When updating, you will get the error:

Could not locate update bundle for com.visualstudio.code.oss within file:///Users/<user>/Library/Caches/com.visualstudio.code.oss.ShipIt/update.<id>/

The new bundle identifier is com.vscodium instead of com.visualstudio.code.oss.

I'm sorry about the issue but we will need to manually update to this version. The next versions will keep com.vscodium so the automatic update will work.

On Windows

The update is executed successfully but you will 2 uninstall instances due to different id: (VSCodium.VSCodium instead of Microsoft.VSCodium)

@GitMensch @paulcarroty What do you think about this issue?

[GitMensch]

I've pinned that issue and referenced it in the GH release.

Win32: Microsoft.VSCodium was bad, the new one is better (I'd prefer VSCodium.vscode, but that's just my taste) - for "updating customers" to have two entries with different version numbers is not "nice", but not a problem in general (to fix this: uninstall the old one, then re-install the new one - either after the automatic update or instead of the automatic update).

macOS -the old one was not necessarily bad, again com.vscodium.code.oss would better match my personal taste

GNU/Linux: while the binaries are available there is no apt update yet (with repo https://download.vscodium.com/debs) - is this related to this issue or just the CDN that needs some time, or even something that must be triggered manually?

If you consider the automatic update broken then maybe ensure that it isn't automatically triggered?

Note: @paulcarroty https://download.vscodium.com/debs opened via browser redirects to https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ which results in a 404, not sure, but maybe this can be adjusted.

[daiyam]

The apt update is updated at 1AM GMT so it hasn't pick up the new release. The 404 is also ok because there is no directory listing. https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/conf/distributions is working fine.

[GitMensch]

Sounds like a directory listing could be added which would also solve the 404, no?

[paulcarroty]

Yeah, the Gitlab Pages auto-index is disabled by default, this can be improved. Triggered the CI retry, so new update will be shipped soon.

If you consider the automatic update broken then maybe ensure that it isn't automatically triggered?

That's for sure, we can add the trigger. I'm busy now, so you both have the maintainer access and can do it.

[goyalyashpal]

Microsoft.VSCodium was bad, the new one is better (I'd prefer VSCodium.vscode, but that's just my taste

umh, i guess VSCodium.VSCodium is good, as it doesn't create confusion. but where's this id used?? :thinking:

[GitMensch]

This id is used in the installer and is used by Windows to store it in the registry. This is later used for updates/changes to the existing entry in "Add/Remove Programs" and a change leads to the old entry not being updated, but instead two entries with different version numbers shown, pointing to the same installation (uninstalling the one which shows the "old" version number will then also uninstall the "new" one).

[msenebald]

Fix for me was to reinstall it.

For homebrew users just brew uninstall vscodium and reinstall with brew install --cask vscodium

[goyalyashpal]

update:

• hiding it myself as offtopic,
• separately as indicated by @daiyam , it is posted on https://github.com/VSCodium/vscodium/discussions/1278

---

offtopic:

View > Stick Scroll requires intellisense extensions (ms-vscode.cpptools and others) to be enabled - wow :)

any alternates to those extensions?

[daiyam]

@yashpalgoyal1304 Could you open a new issue? Thx

[elburro1887]

Fix for me was to reinstall it.

For homebrew users just brew uninstall vscodium and reinstall with brew install --cask vscodium

I did this, but then got

Error: It seems there is already a Binary at '/usr/local/bin/codium'.

So I did:

rm /usr/local/bin/codium
brew install --cask vscodium

and it works now.

[allanbowe]

Also affected on VSCodium, using mac M1:

Could not locate update bundle for com.visualstudio.code.oss within file:///Users/(username)/Library/Caches/com.visualstudio.code.oss.ShipIt/update.10X8mGI/

Re-installing VS Codium appears to have stopped it.

[GitMensch]

As December was some months ago this will now affect less users- and actually there is nothing we can do "more" now, other than letting users know they should uninstall and re-install - therefore... closing.