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
downgrades Node.js version, see Alignment Che-Code with 1.108.x version of VS Code eclipse-che/che#23635 (comment)

What issues does this PR fix?

eclipse-che/che#23635

How to test this PR?

1. Released version of an extension should be installed

Start a 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)

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

Fix #285510

Defaults to 16, this doubles it since sticky scroll takes up another one since that was added. Fixes #285574

Part of #285577

The webgl renderer has a limited number of contexts, because there are potentially many chat terminals and interaction with them is minimal, we don't want to consume one of the contexts. Fixes #285452

Fixes #285329 Fixes #285518

Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>

Fixes #276716

Tighten webgl lifecycle, ensure chat doesn't use

Fixes #233992

Add workspace and session allow options in terminal tool

When navigating to the next/prev problem using editor.action.marker.next, the editor would always scroll the marker to the top of the viewport (using revealPositionNearTop), even if the marker was already visible or just slightly off-screen. This caused a "jumpy" experience and confusion. Changed to use revealPositionInCenterIfOutsideViewport, which maintains context by only scrolling if necessary, and centers the marker if it is significantly far away. Fixes #156782

fix mode changing on edit

* no thinking dropdown for single tool calls * Update src/vs/workbench/contrib/chat/browser/widget/chatContentParts/chatThinkingContentPart.ts Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * for some reason copilot deleted this line --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

github-actions · 2026-02-03T11:00:34Z