Skip to content

chore: upgrade Node to 22.15.1 and VSCode to 1.101.2

Tristan Readrequested to merge
tr/update-nodejs-version-to-22-15-1 into main

Description

Updates the NodeJS versions and minimum VS Code versions. Users on VS Code versions below 1.101.2 will need to update their VS Code version before being able to receive extension updates.

Note: The previous VS Code version (1.100.3) shipped with a lower NodeJS version (v20.19.0) than we currently specify in this project (v22.14.0). Users with a lower versions could encounter unexpected errors with the extension, depending on whether we are already using any NodeJS v21 or v22 features.

The same applies to the Language Server, as that runs on top of the NodeJS version shipped by whichever VS Code version the user is running.

So from one way of looking at it, this version bump does not constitute a reduction in support for any users, it aligns the published VS Code version requirement with what is already the practical restriction.

The purpose of the version bump is to enable more advanced certificate features, see gitlab-org/editor-extensions/gitlab-lsp#1339 (comment 2839915591). It will also enable a NodeJS version bump within the Language Server, which will allow other plugins to make use of the same certificate features, particularly the --use-system-ca flag.

Related Issues

issue: [VS Code] Certificate Trust Store Issues in Con... (#2077) issue: [LSP] Certificate Trust Store Issues in Control... (gitlab-org/editor-extensions/gitlab-lsp#1339)

How has this been tested?

  1. Check out this branch.
  2. Run mise install.
  3. Give the extension a thorough test.
  4. Optional: Install an older version of VS Code (v1.100.2) and observe the behavior.
  • If src/browser or src/common has been modified, please consider interoperability with the Web IDE. See Running the Extension in WebIDE.
  • Consider an end-to-end test for significant new features that aren't covered by integration tests.

Screenshots (if appropriate)

What CHANGELOG entry will this MR create?

  • fix: Bug fix fixes - a user-facing issue in production - included in changelog
  • feature: New feature - a user-facing change which adds functionality - included in changelog
  • BREAKING CHANGE: (fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog
  • None - other non-user-facing changes
Edited by Tristan Read

Merge request reports