Conversation
Bump js-yaml resolution from ^4.3.1 to ^4.3.2 to pick up the fix for GHSA-2883-xcg3-v3hh (CVE-2026-84375): maxTotalMergeKeys does not limit CPU use for empty merge sources.
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
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
1 fixed, 0 ignored, 0 deferred, 0 security pins added, 0 security pins removed, 0 could-not-auto-fix. | label: 🔒 security applied
Fixed
js-yamlresolutionspin inpackage.jsonfrom^4.3.1to^4.3.2so the transitive resolution moves to the patched 4.3.2 (advisory GHSA-2883-xcg3-v3hh / CVE-2026-84375).Ignored
None.
Deferred
None.
Security pins added
None. (The existing
js-yamlresolution inpackage.jsonwas already present; it was tightened to^4.3.2— same major, so no new pin was introduced.)Security pins removed
None. No
# security pinentries exist in anyGemfile.Could not auto-fix
None.
Risks
maxTotalMergeKeys, closing the CPU-exhaustion vector described in the advisory. No public-API changes. Only the tooling pipeline (semantic-releaseand friends) touches this dependency in this repo, and it processes only trusted inputs from CI, so behavior in practice is unchanged.Manual testing
Covered by CI.
Validation
✅ CI green (Actions + commit statuses; app-based checks not monitored)