Reposting the post from another user on a "closed" issue. The issue is not closed at all, we still cannot work after code got updated and that's just absurd. We cannot either revert back cause of the following issue.
I am trying to downgrade the CLI specifically on a remote machine, have tried downloading the CLI tool from the following address:
https://update.code.visualstudio.com/1.85.2/cli-linux-x64/stable
When I run code after unpacking it, it is still looking for the updated GLIBC versions:

[mdefende@c0202 Downloads]$ ./code
./code: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by ./code)
./code: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./code)
./code: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by ./code)
./code: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by ./code)
./code: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by ./code)

I do notice whenever I change the version number, the downloaded file is always named vscode_cli_linux_x64_cli.tar.gz whereas distinct versions of the full VSCode have some distinct tag on their tarballs. For instance, Code 1.85.2 available at https://update.code.visualstudio.com/1.85.2/linux-x64/stable is named code-stable-x64-1705560028.tar.gz whereas 1.85.1 is named code-stable-x64-1702460840.tar.gz . Are all of the CLI links accessing the same 1.86.0 file? I can't check the version or the help of the CLI binary because of the GLIBC errors

EDIT: I tested on an updated Linux distribution and the CLI download links are pointing to the correct versions. However, CLI version 1.85.2 and below (to what I've tested) are still erroring out when they don't find the new GLIBC versions. I don't know what else to try at this point.

• Originally posted by @mdefende in #203967 (comment)*