fix: update js-yaml to 4.3.1 - #16
Draft
Xuuyuan wants to merge 1 commit into
Draft
Conversation
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
1 participant
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 js-yaml from 4.1.1 to 4.3.1 and refresh the pnpm lockfile.
Why
js-yaml 4.x before 4.3.1 is affected by the quadratic
!!omapresolution issue described in GHSA-5p4m-2wfm-xmqj, which tracks the missing backport of the CVE-2026-59870 fix. The data format converter directly passes user-provided YAML toYAML.load().Impact
This is a patch-level dependency update with no application source changes.
Validation
pnpm@9.12.2 install --lockfile-only --frozen-lockfile --ignore-scriptsgit diff --checkFull dependency installation and the full build were intentionally skipped because this repository has a large dependency tree.