Repository navigation
chore: update locked VSCE to 4.1.1 - #1200
Brandon Waterloo (bwateratmsft) wants to merge 1 commit into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.
|
🤖 All 11 changed direct/transitive resolved package versions, including optional/platform signing packages, were independently verified against npm publication timestamps and were published by the cutoff 2026-11-12T23:10:02Z. They reach at least 168 hours of age by the merge time above. Audited head: This records the package-age gate only; it does not authorize or enable merging or auto-merge. |
🤖
Fixes: N/A (no linked issue)
Update the locked
@vscode/vsceresolution from 4.0.0 to 4.1.1 and its required signing packages, preserving the existing*declaration. Audited repository manifests, lockfiles, scripts, and explicit VSCE references; pipelines are unchanged.Independently checked exact npm publication timestamps for all 11 introduced/updated resolved versions, including optional/platform packages: all were published by 2026-11-12T23:10:02Z, reaching 168 hours by 2026-11-19T23:10:02Z. VSCE 4.1.1 was published at 23:10:01.249Z; vsce-sign 2.1.1 at 21:15:53.171Z; all nine platform signing packages 2.0.8 between 18:31:43.710Z and 18:40:31.491Z on November 12. No further lock changes were necessary.
Validated ordinary clean installs, build/type-check, lint, and actual VSIX packaging on Node 22.18 with npm 10.9.3 and npm 11.16.0 at unchanged head
3bfbd5c31a44599ea8ebde28a8db37078bf42977. No compatibility blockers; hosted tests and remote CI were not run locally. No repository review skill was present; reviewed the scoped lock diff directly.Before (base): N/A — nonvisual dependency-lock update.
After (candidate): N/A — nonvisual dependency-lock update.