chore: upgrade to VS Code 1.106 / Electron 37 / Node 22#848
Merged
Conversation
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
2 times, most recently
from
13b55fb to
8699d47
Compare
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
from
8699d47 to
782443d
Compare
- Pin electron and vscode to exact versions to stop Dependabot churn; CI tests minimum (Electron 32) and latest via npx separately - Split CI into extension tests (Electron matrix) and webview tests (own job) since Electron's patched fs.readFileSync crashes vitest's forks pool with jsdom - Add version mapping reference (ewanharris/vscode-versions)
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
from
782443d to
cdb8f94
Compare
EhabY
changed the title
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
from
ffc1309 to
8f1598c
Compare
- Bump engines.vscode to ^1.106.0, engines.node to >= 22 - Update @types/vscode to 1.106.0 (adds SecretStorage.keys()) - Switch to @tsconfig/node22, target node22 in esbuild, lib ES2024 - Unify CI test jobs into single Electron run, simplify pnpm test - Remove --experimental-require-module workaround (native in Node 22) - Run webview tests in Electron alongside extension tests - Restrict release pipeline to tags on main, document pre-release flow - Update CONTRIBUTING.md release instructions and version table
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
from
8f1598c to
5f71b99
Compare
EhabY
changed the title
ThomasK33
approved these changes
Mar 19, 2026
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
from
40af8ca to
de66cc1
Compare
EhabY
force-pushed
the
chore/upgrade-dependencies
branch
from
de66cc1 to
79ccc0d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Breaking: Minimum VS Code version bumped from 1.95 to 1.106 (Electron 32 → 37, Node 20 → 22).
Platform & Tooling
@tsconfig/node22,@types/node@^22,@types/vscode@1.106.0, esbuild targetnode22, libES2024electrondevDependency to37.7.0(matches VS Code 1.106 runtime exactly)pnpm/action-setupfrom v4 to v5 in all CI workflowsDependency Updates
pnpm update+pnpm dedupe@eslint-react/eslint-plugin2.x → 3.x,jsdom28 → 29eslint,typescript-eslint,vitest,vite,ws,@tanstack/react-query,memfs, and othersgetSessionToken()override inCoderApi(base class now provides identical implementation, andnoImplicitOverrideflags it)Workarounds Removed
--experimental-require-moduleflag intest-electron.sh(native in Node 22)pnpm testto a single vitest invocation instead of two sequential processespnpm test:webviewnow runs in Electron (consistent withtest:extension)CI Changes
@types/vscodefrom dependabot ignore list (now exact-pinned)Release Pipeline
v*) now verify the tagged commit is onmainviagit merge-base --is-ancestorv*-pre) can be pushed from any branchfetch-depth: 0to release checkout for ancestry checkDocumentation
pnpm dedupeafterpnpm update