chore(deps): patch high-severity yaml advisories - #1327
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Purpose
Resolve the two actionable high-severity
js-yamlDependabot alerts without widening dependency scope, and record the bounded reachability disposition for the still-unpatchedextract-zipdevelopment-tooling alert.Changes
js-yamllockfile branches:3.15.0 -> 3.15.2under@lhci/utils4.3.0 -> 4.3.2under ESLintextract-zip@2.0.1has no patched releaseRisk disposition
The remaining audit graph is one development-only chain:
@lhci/cli -> lighthouse -> puppeteer-core -> @puppeteer/browsers -> extract-zipTryVit does not import
extract-zipor@puppeteer/browsers. The guarded Lighthouse runner installs pinned Playwright Chromium and supplies its exact executable throughCHROME_PATH, so Puppeteer's browser archive installation path is not invoked. Alert #94 is not dismissed and must be reassessed when upstream removes the package or publishes a patch.Verification
Passed locally:
npm ci --ignore-scriptsnpm ls js-yaml extract-zip --allnpm audit --omit=dev --audit-level=high: 0extract-zipadvisoryFull local Vitest result: 6,895 passed, 19 skipped, one inherited Windows checkout-only failure. The Git blob for
MANROPE-OFL.txtstill matches the certified 4,383 bytes and SHA-256; CRLF expansion makes the Windows working copy 4,476 bytes. Exact-head Linux CI remains the authoritative immutable-byte check.Not run:
Impact