Repository navigation
eng: raise optional VSCE peer minimum to 4.1.1 - #2435
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the optional VSCE peer-minimum update.
No open issues 🎉
1 file not reviewed
eng/package-lock.json: Generated file
What changed in this PR
Raises eng’s optional @vscode/vsce peer minimum from ^4.0.0 to ^4.1.1, keeping VSCE installation consumer-owned.
Changes:
- Updates the peer range in the manifest and synchronizes the lockfile.
- Preserves optional metadata; published dependency metadata and pipeline installation behavior remain unchanged.
| File | Description |
|---|---|
eng/package.json |
Raises the optional VSCE peer requirement to ^4.1.1. |
eng/package-lock.json |
Synchronizes the root peer range with the manifest. |
Review effort: Balanced
|
🤖 Audited head: The npm publication timestamp for VSCE 4.1.1 is |
🤖
Fixes: N/A (requested dependency update; no linked issue).
Raise eng's optional
@vscode/vscepeer minimum from^4.0.0to^4.1.1, preserving optional metadata and synchronizing its npm lockfile. Audited all eight packages; no others directly manage VSCE. Leave published dependency metadata and latest-auto-install pipelines unchanged.Before: Screenshots are not applicable (dependency metadata only); eng accepted VSCE versions below 4.1.1.
After: Screenshots are not applicable; eng requires
^4.1.1when the optional VSCE peer is installed. VSCE 4.1.1 requires Node >=22, compatible with eng's existing >=22.17.0 requirement.Validation from
eng:npm install --package-lock-only --ignore-scripts --no-audit --no-fund— passed; only the root peer range changed.npm ci --no-audit --no-fund— passed; VSCE remains uninstalled when absent.npm run build— passed (ESM and CJS).npm test— initially failed on the 2-second compiler-test startup timeout and cleanup lock.npm test -- --timeout 20000— passed: 41 passing, 5 platform skips.npm run lint— passed.npm pack --dry-run --json— passed: 73 files.Additional Node assertions confirmed matching manifest/lock ranges, retained optional metadata, acceptance of 4.1.1, and rejection of 4.1.0;
git diff --checkpassed. No repository review skill is present. No VSCE publishing operation was run.