fix(deps): raise js-yaml floor to 4.3.1 - #153
Merged
Merged
Conversation
Dependabot flagged js-yaml >= 4.0.0, < 4.3.1 (GHSA-5p4m-2wfm-xmqj, quadratic CPU consumption in !!omap resolution) right after the previous dependency sweep landed. The package reaches us only through dev tooling and already sits in the security override block with a caret range, so the floor moves from ^4.3.0 to ^4.3.1 and stays on the 4.x major its dependents declare. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Resolves the one open Dependabot alert: js-yaml >= 4.0.0, < 4.3.1 (GHSA-5p4m-2wfm-xmqj, high — quadratic CPU consumption in
!!omapresolution, CVE-2026-59870 fix not backported).js-yaml reaches ParseHawk only through dev tooling and already sits in the security override block in
pnpm-workspace.yamlwith a caret range; the floor moves from^4.3.0to^4.3.1, staying on the 4.x major its dependents declare. The lockfile resolves to js-yaml 4.3.1.Verification
pnpm install+pnpm -r build— docs and web both build cleanlyNo Python or runtime code path is affected, so the local runtime verification (
parsehawk restart+just e2e) was not rerun for this change.🤖 Generated with Claude Code
#152