Update to VSCode Fork from 1.81.1 to 1.85.2
What does this MR do and why?
This merge request updates the Web IDE VSCode Fork from 1.81.1 to 1.85.2 by pulling the latest upstream changes.
How to test?
We should test this upgrade in the Web IDE and in the Remote Development Workspaces.
In the Web IDE
- Check out gitlab-web-ide!280 (merged) in your local environment.
- Start the local test server using
yarn start:example
The following video shows a demo of the Web IDE running in 1.85.2:
In Workspaces
Running the VSCode Server varies significantly from system to system, specially in Linux-based systems. Currently, we do not provide support for Alpine-based images, only, Debian-based images with a specific version of GLIBC. You can find the results of testing this upgrade by @vtak in Ubuntu-based systems in #23 (comment 1755249774).
Issues found during this upgrade
- The
gitlab-vscode-nodelessimage doesn't provide the os level libraries required to build VSCode 1.85.2. We've opened an MR to create a new image that satisfies the build requirements gitlab-build-images!760 (merged).
In the Web IDE
Until now, we haven't detected any regressions in the Web IDE with this update. You can use gitlab-web-ide!280 (merged) to test this upgrade in your local environment.
In Workspaces
We discovered that VSCode's system requirements changed significantly after this upgrade. As a result, the VSCode Server can't run on Docker images that used to run VSCode Server v1.81.x. You can read more about this problem and the solutions proposed in #23 (closed).
Related resources
- VSCode Upgrade Issue #21 (closed)
- Merge request to test the VSCode Upgrade in the Web IDE gitlab-web-ide!280 (merged)
- Merge request that creates a new Docker image with the system dependencies expected by the new version of VSCode gitlab-build-images!760 (merged)