Skip to content

fix(deps): Bump js-yaml to 3.15.2 and 4.3.2 - #106

Closed
sentry-junior[bot] wants to merge 1 commit into
mainfrom
fix/bump-js-yaml
Closed

sentry-junior[bot] wants to merge 1 commit into
mainfrom
fix/bump-js-yaml

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

The lockfile pinned two old js-yaml copies, both dev-only:

  • js-yaml@3.14.1 via ava → supertap
  • js-yaml@4.1.0 via eslint and @eslint/eslintrc

Both are in range of advisories GHSA-mh29-5h37-fv8m, GHSA-h67p-54hq-rp68, GHSA-52cp-r559-cp3m, GHSA-5p4m-2wfm-xmqj, and GHSA-2883-xcg3-v3hh. The patched releases (3.15.2 and 4.3.2) already satisfy the existing ^3.14.1 / ^4.1.0 ranges, so this only refreshes package-lock.json (npm update js-yaml). No eslint or ava major bump is needed.

npm audit still flags the 3.x chain because of sprintf-js (GHSA-hp3w-g68c-fv3c, no patched version) under argparse@1. That is a separate advisory. Clearing it would mean moving off ava 5's supertap@3.

via Kedar Vaidya.

--

View Junior Session [Sentry]

Co-Authored-By: Kedar Vaidya <kedar.vaidya@sentry.io>
@kedarv kedarv closed this Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant