Skip to content

Fix npm vulns client vscode#140

Merged
aneshlya merged 2 commits into
mainfrom
fix-npm-vulns-client-vscode
Jun 26, 2026
Merged

Fix npm vulns client vscode#140
aneshlya merged 2 commits into
mainfrom
fix-npm-vulns-client-vscode

Conversation

@aneshlya

Copy link
Copy Markdown
Collaborator

No description provided.

Resolved 13 advisories (8 moderate, 5 high) reported by `npm audit`
via `npm audit fix`. Lock-file-only update; package.json unchanged.
TypeScript compile verified.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@aneshlya aneshlya force-pushed the fix-npm-vulns-client-vscode branch from 54e708d to c016eda Compare June 26, 2026 18:32
The hardcoded `MSBuild <generated>.sln` invocations break when CMake
selects a non-VS generator on the GitHub Actions windows-latest image
(now shipping VS 18 + MSBuild 18), since no .sln gets produced.
Switch to `cmake --build --config Release`, which works with any
generator. Also pass -DCMAKE_BUILD_TYPE=Release so single-config
generators (Ninja, Makefiles) produce Release binaries.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@aneshlya aneshlya merged commit 73ace94 into main Jun 26, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant