Update js-yaml to 4.3.0 - #6
Merged
Merged
Conversation
oshtz
marked this pull request as ready for review
July 26, 2026 16:49
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
js-yamlfrom 4.2.0 to 4.3.0 inpackage-lock.json.Why
Dependabot could not create the security update because its resolver selected an invalid
web-extdowngrade path. npm resolves 4.3.0 within the existing ESLint andweb-extdependency ranges without overrides or apackage.jsonchange.This reduces the full audit from 7 to 6 high-severity development-tooling findings. Production dependencies remain at zero findings, and extension runtime dependencies are unchanged.
Verification
npm cinpm audit --omit=dev --json(0 vulnerabilities)npm run lintnpm test(12 files, 67 tests)npm run build:chromenpm run build:firefoxBoth browser build validators passed.