fix(deps-dev): update vulnerable js-yaml resolutions - #1695
Merged
Changyong Gong (chagong) merged 1 commit intoSep 9, 2026
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Changyong Gong (chagong)
requested review from
Sheng Chen (jdneo),
Jinbo Wang (testforstephen) and
wenyt (wenytang-ms)
as code owners
September 8, 2026 08:29
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
wenyt (wenytang-ms)
approved these changes
Sep 9, 2026
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
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.
Summary
Update only the two development-only
js-yamlresolutions in package-lock.json:mocha -> js-yaml^4.1.0tslint -> js-yaml^3.13.1Generated with
npm update js-yaml --package-lock-only --ignore-scripts --no-fund. Both versions satisfy the existing parent ranges and are outside every open advisory range. Preserves lockfile v2 and its legacy dependency section; no package additions/removals, unrelated dependency changes, manifest changes, or overrides.Dependabot alerts
The refreshed, fully paginated inventory contains exactly these six open alerts:
Validation
On Windows with Node 22.15.1 / npm 10.9.2 and Java 21:
npm ci --no-fund,npm run tslint,npm test(57 passing; one intentional POSIX-only skip),npm run build, andvsce package(VSCE 3.6.1) passed.js-yamlinstance against all six alert ranges.npm audit --omit=dev --package-lock-only --json: zero findings. Full audit retains only the pre-existing low-severitydiffadvisory GHSA-73rr-hh4g-fpgx, mapped to already auto-dismissed alerts 23 and 26; intentionally unchanged. No alert states were modified.CI and review
For head
b31dd22153b5975b0ac0536878e04f532593b745, GitHub Actions CI completed successfully on Linux, macOS, and Windows;license/claalso passed. No external commit statuses or Azure check runs were registered on this head. The Azure Pipelines bot notice says an authorized/azp runcomment may be required; no trigger comment was posted, so Azure validation is not claimed.Copilot review was requested after CI passed and completed with "Copilot wasn't able to review any files in this pull request." Human review is still required.