Skip to content

Fix macOS test launch with VS Code 1.131 - #1684

Merged
StellaHuang95 merged 1 commit into
microsoft:mainfrom
StellaHuang95:fix-macos-vscode-test-launch
Jul 31, 2026
Merged

Fix macOS test launch with VS Code 1.131#1684
StellaHuang95 merged 1 commit into
microsoft:mainfrom
StellaHuang95:fix-macos-vscode-test-launch

Conversation

@StellaHuang95

Copy link
Copy Markdown
Contributor

Why

VS Code 1.131 removed the legacy Contents/MacOS/Electron compatibility path from its macOS application bundle. @vscode/test-electron 2.5.2 still launches that hard-coded path, so all macOS smoke jobs fail with ENOENT before VS Code or the extension starts.

This currently blocks the macOS checks on #1656. The upstream issue and fix are microsoft/vscode-test#349 and microsoft/vscode-test#350.

What

Upgrade @vscode/test-electron from 2.5.2 to 3.1.0 and refresh the lockfile. Version 3.1.0 resolves the macOS executable from CFBundleExecutable in Info.plist, with the old Electron path retained as a fallback for older VS Code builds.

This is a development-only dependency change. Version 3.1.0 requires Node 22, which is already used by CI.

Validation

  • npm run compile-tests
  • npm run unittest — 1469 passing, 0 failing, 5 pending

Upgrade @vscode/test-electron to 3.1.0 so macOS CI resolves the executable declared by VS Code 1.131 instead of the removed Electron compatibility path.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 39dcc6a3-0fbd-4f36-9d0f-68677de49c27
@StellaHuang95
StellaHuang95 merged commit 58f231d into microsoft:main Jul 31, 2026
47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants