Che-Code shouldn't suggests updating the built-in extensions

Is your task related to a problem? Please describe

When the user launches Che-Code, it always includes the same versions of all the VS Code built-ins - v1.0.0. E.g.:

So, Che-Code suggests the user update the built-ins:

The updated extensions are version v1.64.0-next.68976705968:

See more details at the https://github.com/eclipse/che/issues/21787#issuecomment-1310553820 below.

Describe the solution you’d like

Need to figure out how we can include the latest versions of the VS Code built-ins into Che-Code without suggesting the user update all the extensions.

Describe alternatives you’ve considered

No response

Additional context

Note, that VS Code (Electron) includes the built-ins of version v1.0.0 and doesn’t suggest the user update it.

[azatsarynnyy]

I’ve just found there is a closed OpenVSX issue https://github.com/eclipse/openvsx/issues/446 that was fixed by https://github.com/eclipse/openvsx/pull/449. It seems that the patch has been deployed recently to the production registry instance. Now, all the extensions from the vscode namespace shouldn’t be returned by OpenVSX API. For more details, see https://github.com/eclipse/openvsx/blob/ee6eb3b102dfd75c126cc1ef74a228bc8b999fff/server/src/main/java/org/eclipse/openvsx/adapter/LocalVSCodeService.java#L48

I’m closing this issue as not reproducible anymore.

[azatsarynnyy]

Now, my understanding of the problem is much better. I updated the issue title and its description respectively.

There are two important parts.

1. The extensions registry.

• The official VS Code’s Marketplace does not include VS Code’s built-in extensions. It makes sense as all the extensions of the specific version are already bundled in the VS Code of the corresponding version. There is no need to update such extensions manually.
• OpenVSX includes VS Code’s built-in extensions. And it makes sense for Eclipse Theia for example. Because Theia downloads VS Code’s built-ins from OpenVSX.

1. Version of the built-ins. VS Code includes the built-in extensions that always have version v1.0.0, as it does not affect anything. The built-ins published to OpenVSX have the version that corresponds to a specific VS Code version, e.g. 1.62.3. So, VS Code thinks that there are updates available for its built-ins.

We discussed these problems with @RomanNikitenko and we think there are two possible solutions:

1. Teach VS Code to skip checking the updates for its built-ins.
2. When we package Che-Code into the image, we can update the version: attribute of the built-ins to the current version.

The 2’nd approach looks more reasonable as we don’t need to touch VS Code internals. So, we’ll move forward with it.