chore(deps): bump js-yaml resolution to ^4.3.0 (dev-only advisory)#6486
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
🤖 This preview updates automatically when you update the PR. |
Contributor
antonis
marked this pull request as ready for review
July 21, 2026 10:57
alwx
approved these changes
Jul 22, 2026
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.
📢 Type of change
📜 Description
Bumps the
js-yamlresolution from^4.2.0to^4.3.0, resolvingjs-yamlto4.3.0in the lockfile.This addresses GHSA / high-severity advisory: "YAML merge-key chains can force quadratic CPU consumption" (affects
js-yaml >=4.0.0 <4.3.0). The vulnerable copy (4.2.0) was pulled transitively vialerna@8.1.8.💡 Motivation and Context
Dependabot flagged this transitive advisory. The affected package is dev/build tooling only (
lerna, used for releases) — it is not part of the shipped@sentry/react-nativeruntime, whose production dependency tree audits clean. This is a defensive bump to keep the dev toolchain free of known advisories.💚 How did you test it?
yarn install --immutablepasses (lockfile in sync).yarn npm audit --recursiveno longer reports thejs-yamladvisory.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Companion PRs bump the other easy dev-only transitive advisories (
brace-expansion,cross-spawn,glob). The remainingsigstore/@octokit/*/uuidadvisories are bundled deep inlernaand are best handled by a separate lerna upgrade.