Bump js-yaml from 3.15.0 to 3.15.2 in /tests/workflows - #2704
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 3.15.0 to 3.15.2. - [Changelog](https://github.com/nodeca/js-yaml/blob/3.15.2/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.15.0...3.15.2) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 3.15.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Hello dependabot[bot],My role is to assist you with the merge of this Available options
Available commands
Status report is not available. The following options are set: bypass_author_approval, bypass_jira_check |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: bypass_author_approval, bypass_jira_check |
There was a problem hiding this comment.
Dependency Bump Evaluation
Version change: js-yaml 3.15.0 -> 3.15.2 (patch)
Scope: tests/workflows/yarn.lock only — no source code changes
Changes:
- 3.15.1: [Security] Backport fix for quadratic complexity in
!!omapduplicate key detection (DoS mitigation) - 3.15.2: [Security] Backport merge sequence size hard-limit (100) and count empty mappings toward
maxTotalMergeKeysto limit CPU usage (#797)
Breaking changes: None
Security concerns: None — this PR fixes two CPU/DoS vulnerabilities (backports from v5.4.1)
Impact on codebase: Negligible. js-yaml is not directly imported in any source file; it is a transitive dependency only. The change is confined to the test workflow lockfile.
CI status: dependency-review and prettier passed. test, CodeQL, and Test GitHub Actions workflows still in progress at time of review.
Recommendation: SAFE TO MERGE
— Claude Code
Bumps js-yaml from 3.15.0 to 3.15.2.
Changelog
Sourced from js-yaml's changelog.
Commits
5c45bd63.15.2 released5a708f9dist rebuild3485bc0Backport merge limits from v5.4.1f34812fUpdate .gitignoreab85ae23.15.1 released30a5e76dist rebuild22a8071Backport quadratic complexity fix for !!omapDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.