Alignment with 1.108.2 version of VS Code by RomanNikitenko · Pull Request #646 · che-incubator/che-code

RomanNikitenko · 2026-02-02T13:25:32Z

TODO

What does this PR do?

alignment with 1.108 release branch of the upstream: https://github.com/microsoft/vscode/tree/release/1.108

What issues does this PR fix?

eclipse-che/che#23635

How to test this PR?

Test any functionality, I tested the following:

open a file
create a default terminal
create a terminal in a container
instal an extension
uninstall an extension
run a devfile command
run a command from the Command Palette
Git Clone flow from the Command Palette

I've tested the following use cases:

1. Released version of an extension should be installed

Start workspace https://workspaces.openshift.com#https://github.com/che-incubator/quarkus-api-example?new&editor-image=quay.io/che-incubator-pull-requests/che-code:pr-646-amd64
Check that released versions of the Quarkus and Language Support for Java extensions are installed
Check there is no error at the GitHub Pull Requests extension activation, see Alignment Che-Code with 1.108.x version of VS Code eclipse-che/che#23635 (comment)

2. Chat icon

Start workspace https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com#https://github.com/RomanNikitenko/web-nodejs-sample?new&editor-image=quay.io/che-incubator-pull-requests/che-code:pr-646-amd64
Check that Chat icon is displayed by default in the Command Center area

Check that it's still possible to hide the icon using chat.commandCenter.enabled setting

Add vscode-editor-configurations ConfigMap to your namespace:

vscode-editor-configurations ConfigMap

kind: ConfigMap
apiVersion: v1
metadata:
 name: vscode-editor-configurations
 namespace: eclipse-che
 labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: workspaces-config
data:
  settings.json: |
    {
      "chat.commandCenter.enabled": false
    }

Restart workspace
Check the icon is not displayed anymore

3. Ability to manage extensions installation using a ConfigMap

4. Ansible-related use case

Test use case described in Fix path in in generating extension callback URL #532

5. Default extensions should be installed when "Install from VSIX" is disabled (see #617)

Add default-extensions ConfigMap to your namespace:

default-extensions ConfigMap

kind: ConfigMap
apiVersion: v1
metadata:
  name: default-extensions
  labels:
    controller.devfile.io/mount-to-devworkspace: 'true'
    controller.devfile.io/watch-configmap: 'true'
  annotations:
     controller.devfile.io/mount-as: env
data:
  DEFAULT_EXTENSIONS: '/tmp/atlassian.atlascode-3.0.10.vsix;/tmp/snowflake.snowflake-vsc-1.9.1.vsix'

Add vscode-editor-configurations ConfigMap to your namespace:

vscode-editor-configurations ConfigMap

kind: ConfigMap
apiVersion: v1
metadata:
  name: vscode-editor-configurations
  namespace: eclipse-che
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: workspaces-config
data:
  configurations.json: |
    {
      "extensions.install-from-vsix-enabled": false
    }

Start workspace https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#https://github.com/RomanNikitenko/web-nodejs-sample/tree/install-extensions-from-vsix?editor-image=quay.io/che-incubator-pull-requests/che-code:pr-646-amd64
Check: Extensions panel => ... => Install from VSIX action is absent
Check: Extensions panel => Atlassian, Snowflake and YAML extensions are installed as default extensions

6. Test starting a workspace and basic functionality for the following images

Image	Workspace starts	Link to start a workspace
	udi
quay.io/devfile/universal-developer-image:ubi8-latest	🟢	click here
quay.io/devfile/universal-developer-image:ubi9-latest	🟢	click here
quay.io/devfile/universal-developer-image:ubi10-latest	🟢	click here
	ubi-8
registry.access.redhat.com/ubi8-minimal:latest	🟢	click here
registry.access.redhat.com/ubi8-minimal:8.10	🟢	click here
registry.access.redhat.com/ubi8-minimal:8.9	🟢	click here
	ubi-9
registry.access.redhat.com/ubi9-minimal:latest	🟢	click here
registry.access.redhat.com/ubi9-minimal:9.7	🟢	click here
registry.access.redhat.com/ubi9-minimal:9.6	🟢	click here
	ubi-10
registry.access.redhat.com/ubi10-minimal:latest	🟢	click here
registry.access.redhat.com/ubi10-minimal:10.1	🟢	click here
registry.access.redhat.com/ubi10-minimal:10.0	🟢	click here

Does this PR contain changes that override default upstream Code-OSS behavior?

the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
the corresponding items were added to the CHANGELOG.md file
rules for automatic git rebase were added to the .rebase folder

@xterm/xterm@6.1.0-beta.77

Auto approve npm scripts from workspace package.json by default

npm scripts will be approved automatically with #285509. For npx we probably don't want to auto approve.

…ion.ps1 Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Remove unnecessary auto approve rules

…View

Editor GPU: Support rendering strikethrough

Use executable bit when completing commands in terminal suggest

Fix: Replace terminal tabbed view lifecycle hack with Event.once

Fix: Replace terminal view lifecycle hack with Event.once

…mmands Fix auto-approve to suggest commands with flags when flags precede subcommand

github-actions · 2026-03-26T20:41:31Z